How to make sub-project build/participation easier?

[Yang ZHONG <le...@gmail.com>]

I was trying to build SDO stand-alone.
It always complained parent-2-incubator-SNAPSHOT.pom can't be downloaded.

Thanks to Raymond for pointing out parent-2-incubator-SNAPSHOT.pom is a
generated artifact.

In order to build at root to generate parent-2-incubator-SNAPSHOT.pom,
I had to download and build too many sub-projects including SCA, DAS,
spec/SCA, spec/DAS?, distribution/SCA, sampleapps and samples.

Even if it's a one-time setup,
is there any way to make sub-project build/participation easier please?
If yes, can we document that please?

-- 

Yang ZHONG

Re: How to make sub-project build/participation easier?

[Venkata Krishnan <fo...@gmail.com>]

Hi Yang,

Really not sure if you bulid SCA and DAS to get thro to SDO.  There was a
mail from Jeremy were he put down the order in which these things should be
built.... will see if I can trace that.  But I vividly remember having to
build SDO for SCA and not viceversa.

- Venkat

On 12/5/06, Yang ZHONG <le...@gmail.com> wrote:
>
> I was trying to build SDO stand-alone.
> It always complained parent-2-incubator-SNAPSHOT.pom can't be downloaded.
>
> Thanks to Raymond for pointing out parent-2-incubator-SNAPSHOT.pom is a
> generated artifact.
>
> In order to build at root to generate parent-2-incubator-SNAPSHOT.pom,
> I had to download and build too many sub-projects including SCA, DAS,
> spec/SCA, spec/DAS?, distribution/SCA, sampleapps and samples.
>
> Even if it's a one-time setup,
> is there any way to make sub-project build/participation easier please?
> If yes, can we document that please?
>
> --
>
> Yang ZHONG
>
>

Re: How to make sub-project build/participation easier?

[kelvin goodson <ke...@gmail.com>]

I have done this for parent pom and buildtools.
Regards, Kelvin.

On 05/12/06, Jeremy Boynes <jb...@apache.org> wrote:
>
> On Dec 5, 2006, at 1:38 AM, kelvin goodson wrote:
>
> > I had a little dig around and I'm tring to work out if the purpose
> > of the
> > people.apache.org m2-snapshot-repository is right for solving this
> > issue.
> > If we can post an incubator-SNAPSHOT version of buildtools and
> > parent pom
> > there, then I think that would solve this issue.
>
> +1
>
> I think we should start publishing occasional snapshots of trunk
> projects to the snapshot repo so that most modules can be built
> separately.
>
> --
> Jeremy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>

Re: How to make sub-project build/participation easier?

[Jeremy Boynes <jb...@apache.org>]

On Dec 6, 2006, at 3:57 AM, kelvin goodson wrote:

> I pressed send too early on my last note.
>
> So now we have a version of the parent pom with the 2-incubator- 
> SNAPSHOT
> version tag and a version of buildtools with the
> 1.0-incubator-SNAPSHOTavailable from the m2-snapshot-repository,
> meaning that you no longer need
> to do a source build on these projects to get the artifacts into  
> your local
> repo. All of the Tuscany java projects depend on these artifacts.

Thanks Kelvin.

In general though, our cross-module dependencies should not be on  
SNAPSHOTs but on released versions. For example, I don't think  
buildtools has changed since M2 and so we could rely on the stable M2  
version. Similarly DAS and SCA would be better to rely on the M2  
version of SDO, at least until they need some of the new function.

>
> We'll need to be aware that if we change anything in these projects  
> we ought
> to update the snapshot repo.  I have done a chmod 755 on the directory
> hierarchies in the repository so that other committers can make the  
> updates
> if and when necessary.

I have a section in my ~/.m2/settings.xml file that does that  
automatically during "deploy":
<settings>
   <servers>
     <server>
       <id>apache.releases</id>
       <directoryPermissions>775</directoryPermissions>
       <filePermissions>644</filePermissions>
     </server>
     ... repeated for each repo we deploy to ...

I'm not sure if this can be specified in the <distributionManagement>  
section.

--
Jeremy


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org

Re: How to make sub-project build/participation easier?

[kelvin goodson <ke...@gmail.com>]

I pressed send too early on my last note.

So now we have a version of the parent pom with the 2-incubator-SNAPSHOT
version tag and a version of buildtools with the
1.0-incubator-SNAPSHOTavailable from the m2-snapshot-repository,
meaning that you no longer need
to do a source build on these projects to get the artifacts into your local
repo. All of the Tuscany java projects depend on these artifacts.

We'll need to be aware that if we change anything in these projects we ought
to update the snapshot repo.  I have done a chmod 755 on the directory
hierarchies in the repository so that other committers can make the updates
if and when necessary.

Regards, Kelvin.

On 05/12/06, Jeremy Boynes <jb...@apache.org> wrote:
>
> On Dec 5, 2006, at 1:38 AM, kelvin goodson wrote:
>
> > I had a little dig around and I'm tring to work out if the purpose
> > of the
> > people.apache.org m2-snapshot-repository is right for solving this
> > issue.
> > If we can post an incubator-SNAPSHOT version of buildtools and
> > parent pom
> > there, then I think that would solve this issue.
>
> +1
>
> I think we should start publishing occasional snapshots of trunk
> projects to the snapshot repo so that most modules can be built
> separately.
>
> --
> Jeremy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>

Re: How to make sub-project build/participation easier?

[Jeremy Boynes <jb...@apache.org>]

On Dec 5, 2006, at 1:38 AM, kelvin goodson wrote:

> I had a little dig around and I'm tring to work out if the purpose  
> of the
> people.apache.org m2-snapshot-repository is right for solving this  
> issue.
> If we can post an incubator-SNAPSHOT version of buildtools and  
> parent pom
> there, then I think that would solve this issue.

+1

I think we should start publishing occasional snapshots of trunk  
projects to the snapshot repo so that most modules can be built  
separately.

--
Jeremy

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org

Re: How to make sub-project build/participation easier?

[kelvin goodson <ke...@gmail.com>]

I had a little dig around and I'm tring to work out if the purpose of the
people.apache.org m2-snapshot-repository is right for solving this issue.
If we can post an incubator-SNAPSHOT version of buildtools and parent pom
there, then I think that would solve this issue.
These should be the only two that you need to build in the absence of
downloadable versions (Note that building the pukka M2 source distribution
requires no action on the part of the builder since the buildtools and
parent pom M2 artifacts are available from the m2-incubating-repository)

Regards, Kelvin.

On 04/12/06, Yang ZHONG <le...@gmail.com> wrote:
>
> I was trying to build SDO stand-alone.
> It always complained parent-2-incubator-SNAPSHOT.pom can't be downloaded.
>
> Thanks to Raymond for pointing out parent-2-incubator-SNAPSHOT.pom is a
> generated artifact.
>
> In order to build at root to generate parent-2-incubator-SNAPSHOT.pom,
> I had to download and build too many sub-projects including SCA, DAS,
> spec/SCA, spec/DAS?, distribution/SCA, sampleapps and samples.
>
> Even if it's a one-time setup,
> is there any way to make sub-project build/participation easier please?
> If yes, can we document that please?
>
> --
>
> Yang ZHONG
>
>