[Build] philosophy behind the myfaces build ?

[Matthias Wessendorf-4]

Hi,

when doing a checkout of myfaces, pretty much everything is build.
Fine.
Except Trinidad and Tobago. No problem with that.

But, when just updating a single svn-folder, like tomahawk, there is a very
high chance that the build pretty much fails. Why? because it depends
on snapshots that are build via the "master myfaces" build.

In this case I am refering to the myfaces-builder plugin.

Isn't is kinda annoying that you always have to build all?
Just b/c of a snapshot dependency?
At least to me.

Why not "testing" the builder-snapshot in a branch (like
tomahawk-move-to-builder-branch).
Do a builder release, once stable. And update trunk.  (I am only using
builder-plug as an example).

That's what we do for Trinidad. It doesn't depend on a snapshot
plugin, so it is easy (and
straightforward) to build it.

Not sure why there is this, build the world first philosophy :-)

What do you think ?

--
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org

Matthias Wessendorf schrieb:

> Hi,
>
> when doing a checkout of myfaces, pretty much everything is build.
> Fine.
> Except Trinidad and Tobago. No problem with that.
>
> But, when just updating a single svn-folder, like tomahawk, there is a very
> high chance that the build pretty much fails. Why? because it depends
> on snapshots that are build via the "master myfaces" build.
>
> In this case I am refering to the myfaces-builder plugin.
>
> Isn't is kinda annoying that you always have to build all?
> Just b/c of a snapshot dependency?
> At least to me.
>
> Why not "testing" the builder-snapshot in a branch (like
> tomahawk-move-to-builder-branch).
> Do a builder release, once stable. And update trunk.  (I am only using
> builder-plug as an example).
>
> That's what we do for Trinidad. It doesn't depend on a snapshot
> plugin, so it is easy (and
> straightforward) to build it.
>
> Not sure why there is this, build the world first philosophy :-)
>
> What do you think ?
>
>  

Add the following to ~/.m2/settings.xml. Then add "-Papachesnap" when
building a project.

This allows maven to download stuff published to the snapshot
repository. Which is kind of useful when building snapshot projects :-)

<settings>
  <profiles>
    <profile>
      <id>apachesnap</id>
      <repositories>
        <repository>
          <id>apache.org</id>
          <name>Maven Snapshots</name>
          <url>http://people.apache.org/repo/m2-snapshot-repository</url>
          <releases>
            <enabled>false</enabled>
          </releases>
          <snapshots>
            <enabled>true</enabled>
          </snapshots>
        </repository>
      </repositories>
      <pluginRepositories>
        <pluginRepository>
          <id>apache.org</id>
          <name>Maven Plugin Snapshots</name>
          <url>http://people.apache.org/repo/m2-snapshot-repository</url>
          <releases>
            <enabled>false</enabled>
          </releases>
          <snapshots>
            <enabled>true</enabled>
          </snapshots>
        </pluginRepository>
      </pluginRepositories>
    </profile>
  </profiles>
</settings>

Regards,
Simon

[Manfred Geiler]

What matthias ment was, that we should rather have no
myfaces-inter-subproject-snapshot-dependencies.
I second that. The trunk of a MyFaces sub-project should always depend
on release versions of other projects UNLESS there is a good reason
for having a dependency to a snapshot.
What reasons are there?
1. the other project has a new feature we depend on and has not yet released
2. there is no release yet of the other project
3. ...more?

In all cases the snapshot dependency should be a temporary option and
as soon as the other is released we should switch to release
dependency (again).

--Manfred


On Mon, Jun 16, 2008 at 8:55 AM, simon.kitching@...
<simon.kitching@...> wrote:

> Matthias Wessendorf schrieb:
>> Hi,
>>
>> when doing a checkout of myfaces, pretty much everything is build.
>> Fine.
>> Except Trinidad and Tobago. No problem with that.
>>
>> But, when just updating a single svn-folder, like tomahawk, there is a very
>> high chance that the build pretty much fails. Why? because it depends
>> on snapshots that are build via the "master myfaces" build.
>>
>> In this case I am refering to the myfaces-builder plugin.
>>
>> Isn't is kinda annoying that you always have to build all?
>> Just b/c of a snapshot dependency?
>> At least to me.
>>
>> Why not "testing" the builder-snapshot in a branch (like
>> tomahawk-move-to-builder-branch).
>> Do a builder release, once stable. And update trunk.  (I am only using
>> builder-plug as an example).
>>
>> That's what we do for Trinidad. It doesn't depend on a snapshot
>> plugin, so it is easy (and
>> straightforward) to build it.
>>
>> Not sure why there is this, build the world first philosophy :-)
>>
>> What do you think ?
>>
>>
> Add the following to ~/.m2/settings.xml. Then add "-Papachesnap" when
> building a project.
>
> This allows maven to download stuff published to the snapshot
> repository. Which is kind of useful when building snapshot projects :-)
>
> <settings>
>  <profiles>
>    <profile>
>      <id>apachesnap</id>
>      <repositories>
>        <repository>
>          <id>apache.org</id>
>          <name>Maven Snapshots</name>
>          <url>http://people.apache.org/repo/m2-snapshot-repository</url>
>          <releases>
>            <enabled>false</enabled>
>          </releases>
>          <snapshots>
>            <enabled>true</enabled>
>          </snapshots>
>        </repository>
>      </repositories>
>      <pluginRepositories>
>        <pluginRepository>
>          <id>apache.org</id>
>          <name>Maven Plugin Snapshots</name>
>          <url>http://people.apache.org/repo/m2-snapshot-repository</url>
>          <releases>
>            <enabled>false</enabled>
>          </releases>
>          <snapshots>
>            <enabled>true</enabled>
>          </snapshots>
>        </pluginRepository>
>      </pluginRepositories>
>    </profile>
>  </profiles>
> </settings>
>
> Regards,
> Simon
>
>

--
http://www.irian.at
Your JSF powerhouse - JSF Consulting,
Development and Courses in English and
German

Professional Support for Apache MyFaces

[Matthias Wessendorf-2]

+1

It *can* be a pain in the butt to "just" run the build on subproject.

-M

Sent from my iPod.

Am 09.07.2008 um 21:35 schrieb "Manfred Geiler" <manfred.geiler@...
 >:

> What matthias ment was, that we should rather have no
> myfaces-inter-subproject-snapshot-dependencies.
> I second that. The trunk of a MyFaces sub-project should always depend
> on release versions of other projects UNLESS there is a good reason
> for having a dependency to a snapshot.
> What reasons are there?
> 1. the other project has a new feature we depend on and has not yet  
> released
> 2. there is no release yet of the other project
> 3. ...more?
>
> In all cases the snapshot dependency should be a temporary option and
> as soon as the other is released we should switch to release
> dependency (again).
>
> --Manfred
>
>
> On Mon, Jun 16, 2008 at 8:55 AM, simon.kitching@...
> <simon.kitching@...> wrote:
>> Matthias Wessendorf schrieb:
>>> Hi,
>>>
>>> when doing a checkout of myfaces, pretty much everything is build.
>>> Fine.
>>> Except Trinidad and Tobago. No problem with that.
>>>
>>> But, when just updating a single svn-folder, like tomahawk, there  
>>> is a very
>>> high chance that the build pretty much fails. Why? because it  
>>> depends
>>> on snapshots that are build via the "master myfaces" build.
>>>
>>> In this case I am refering to the myfaces-builder plugin.
>>>
>>> Isn't is kinda annoying that you always have to build all?
>>> Just b/c of a snapshot dependency?
>>> At least to me.
>>>
>>> Why not "testing" the builder-snapshot in a branch (like
>>> tomahawk-move-to-builder-branch).
>>> Do a builder release, once stable. And update trunk.  (I am only  
>>> using
>>> builder-plug as an example).
>>>
>>> That's what we do for Trinidad. It doesn't depend on a snapshot
>>> plugin, so it is easy (and
>>> straightforward) to build it.
>>>
>>> Not sure why there is this, build the world first philosophy :-)
>>>
>>> What do you think ?
>>>
>>>
>> Add the following to ~/.m2/settings.xml. Then add "-Papachesnap" when
>> building a project.
>>
>> This allows maven to download stuff published to the snapshot
>> repository. Which is kind of useful when building snapshot  
>> projects :-)
>>
>> <settings>
>> <profiles>
>>   <profile>
>>     <id>apachesnap</id>
>>     <repositories>
>>       <repository>
>>         <id>apache.org</id>
>>         <name>Maven Snapshots</name>
>>         <url>http://people.apache.org/repo/m2-snapshot-repository</
>> url>
>>         <releases>
>>           <enabled>false</enabled>
>>         </releases>
>>         <snapshots>
>>           <enabled>true</enabled>
>>         </snapshots>
>>       </repository>
>>     </repositories>
>>     <pluginRepositories>
>>       <pluginRepository>
>>         <id>apache.org</id>
>>         <name>Maven Plugin Snapshots</name>
>>         <url>http://people.apache.org/repo/m2-snapshot-repository</
>> url>
>>         <releases>
>>           <enabled>false</enabled>
>>         </releases>
>>         <snapshots>
>>           <enabled>true</enabled>
>>         </snapshots>
>>       </pluginRepository>
>>     </pluginRepositories>
>>   </profile>
>> </profiles>
>> </settings>
>>
>> Regards,
>> Simon
>>
>>
>
>
>
> --
> http://www.irian.at
> Your JSF powerhouse - JSF Consulting,
> Development and Courses in English and
> German
>
> Professional Support for Apache MyFaces

[Jürgen Jatzkowski]

+1

No question: it is a pain in the butt. And there seems to be no good reason for this as given by Manfred's definition. Right?

Jürgen

Matthias Wessendorf-2 wrote:

+1

It *can* be a pain in the butt to "just" run the build on subproject.

-M

Sent from my iPod.

Am 09.07.2008 um 21:35 schrieb "Manfred Geiler" <[e-mail]
 >:

> What matthias ment was, that we should rather have no
> myfaces-inter-subproject-snapshot-dependencies.
> I second that. The trunk of a MyFaces sub-project should always depend
> on release versions of other projects UNLESS there is a good reason
> for having a dependency to a snapshot.
> What reasons are there?
> 1. the other project has a new feature we depend on and has not yet  
> released
> 2. there is no release yet of the other project
> 3. ...more?
>
> In all cases the snapshot dependency should be a temporary option and
> as soon as the other is released we should switch to release
> dependency (again).
>
> --Manfred
>
>