thanks!
Matthias Wessendorf wrote:
Hey,
ok, the 2.0.0.1 branch has been renamed to "trinidad-2.0.x"
So this URL contains our "kinda" *trunk (for Trinidad's JSF 2.0 stuff):
https://svn.apache.org/repos/asf/myfaces/trinidad/branches/trinidad-2.0.x/
The previous "trinidad-2.0.x" has been renamed to "ex-trinidad-2.0.x" and I will
delete it by end of Friday, unless I hear different here.
-Matthias
On Wed, Jan 6, 2010 at 5:23 PM, Andrew Robinson
<[email protected]> wrote:
Yeah I am confused by this as well as 2.0.x is now 2.0.1-SNAPSHOT, so
why would that not be the place to keep working?
On Tue, Jan 5, 2010 at 2:55 PM, Gabrielle Crawford
<[email protected]> wrote:
Hmmmm, so this means if we're working on 2.0 we need to pull a new branch
each time you release, right? I guess I would like it if trinidad-2.0.x
branch is always the 2.0 "trunk", and 2.0.0.0, 2.0.0.1, etc is branched off
of there, so I don't have to check out a new branch every time we release.
Maybe this is too hard given that you're merging the 1.2 code changes into
the 2.0 branch?
Thanks,
Gab
Matthias Wessendorf wrote:
as you noticed, the trinidad 2.0.0 alpha is now on the vote;
the "new" location for the ongoing working branch is located here:
https://svn.apache.org/repos/asf/myfaces/trinidad/branches/2.0.0.1-branch/
-Matthias
On Tue, Jan 5, 2010 at 10:04 AM, Matthias Wessendorf <[email protected]>
wrote:
Hi,
we are on the middle of releasing a first version of the JSF 2.0-based
Trinidad plugins.
As of that I updated the Trinidad 2.0 branch to reflect that.
How to use the tmp version, on the branch ?
Use the stage repo inside your pom.xml file:
...
<pluginRepositories>
<pluginRepository>
<id>apache.stage</id>
<name>Apache Stage Repository</name>
<url>http://people.apache.org/~matzew/plugins_2_0_0/</url>
<layout>default</layout>
</pluginRepository>
</pluginRepositories>
...
or... you can check out the TAG ([1]) and built it from there.
Thanks!
Matthias
[1]
http://svn.apache.org/repos/asf/myfaces/trinidad-maven/tags/maven-plugin-parent-2.0.0/
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
