You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Sean Schofield <se...@gmail.com> on 2006/02/11 16:23:37 UTC
[maven] Issue with Core Release
I've released commons and I'm trying to *prepare* the core project for
release. I'm running into some difficulty though.
[ERROR] BUILD ERROR
[INFO] -------------------------------------------------------------------------
---
[INFO] Can't release project due to non released dependencies :
org.apache.myfaces.commons:myfaces-commons:jar:1.1.3-SNAPSHOT
org.codehaus.mojo:xslt-maven-plugin:maven-plugin:1.0-SNAPSHOT
The biggest issue is the XSLT plugin. That is a snapshot and its not
a myfaces plugin. The only solution I can think of is to add it to
the maven project as our own plugin and release it (with a myfaces
group id.) Then when they finally get around to releasing the plugin
we could switch to the official one.
The second issue is the commons snapshot. When you prepare the
release, maven wants to create a branch (or tag.) It switches from a
snapshot to final version on the branch poms and then increments the
snapshot version on the trunk.
The problem is that I don't want to change to a non snapshot version
on the trunk just to create the branch (and then change it back
again.) I'm pretty sure I didn't do this for the master-pom
dependency when preparing the commons release.
Any insight?
Sean
Re: [maven] Issue with Core Release
Posted by Sean Schofield <se...@gmail.com>.
Hehehe I knew Bernd would go crazy at that suggestion. :-)
@Manfred: SNAPSHOT has a special connatation in Maven. So if you want
to call it alpha or whatever, you can just do that. But SNAPSHOT
tells Maven to keep checking for a newer version, etc.
I will see if I can find the codehaus mailing list and ask if they
can't release it as alpha. SIGH ... another mailing list.
Sean
On 2/11/06, Bernd Bohmann <be...@atanion.com> wrote:
> I would never allow to patch the release plugin to accept a SNAPSHOT
> version. You don't need to use the final version you can use a released
> version but never a SNAPSHOT.(The release version maybe a alpha or beta
> release)
>
> Regards
>
> Bernd
>
> Manfred Geiler schrieb:
> > Yes, I agree with Martin.
> > Perhaps a better way would be to patch the release plugin so that it
> > accepts SNAPSHOTs. Since I have dived into maven this week for a
> > rather complex project at my company, I'm no longer a total maven
> > newby. Hope I can afford some time next week to bring in my new
> > knowledge into MyFaces. As as starter I can have a look at the release
> > plugin sourcecode and see what's possible - but not before monday.
> >
> > WDYT?
> >
> > Manfred
> >
> >
> > On 2/11/06, Martin Marinschek <ma...@gmail.com> wrote:
> >
> >>I don't even see why you need to be forced to use the final version of
> >>a plugin - you can have an alpha-state plugin doing something on a
> >>very mature project.
> >>
> >>regards,
> >>
> >>Martin
> >>
> >>On 2/11/06, Sean Schofield <se...@gmail.com> wrote:
> >>
> >>>I also posted about issue on the maven dev list. There is definitely
> >>>room for improvement in the release plugin. It doesn't really
> >>>envision you creating a branch for a release that will be down the
> >>>road some time. I don't see why we need to switch to final versions
> >>>of a plugin until we are actually ready to release. Of course we
> >>>could skip the plugin but maven automates some of the important tasks
> >>>for you.
> >>>
> >>>Sean
> >>>
> >>>On 2/11/06, Matthias Wessendorf <mw...@gmail.com> wrote:
> >>>
> >>>>>The biggest issue is the XSLT plugin. That is a snapshot and its not
> >>>>>a myfaces plugin. The only solution I can think of is to add it to
> >>>>>the maven project as our own plugin and release it (with a myfaces
> >>>>>group id.) Then when they finally get around to releasing the plugin
> >>>>>we could switch to the official one.
> >>>>
> >>>>I am not that maven guy, but this kind of *work around* sounds ok for me.
> >>>>
> >>>>-Matthias
> >>>>
> >>>
> >>
> >>--
> >>
> >>http://www.irian.at
> >>
> >>Your JSF powerhouse -
> >>JSF Consulting, Development and
> >>Courses in English and German
> >>
> >>Professional Support for Apache MyFaces
> >>
> >
> >
>
> --
> Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development
> Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com
> phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333
>
Re: [maven] Issue with Core Release
Posted by Sean Schofield <se...@gmail.com>.
Someone on the maven dev list said they would try and publish an alpha
release for us sometime soon. So for now I think we should stick with
the plugin until we are closer to the release.
Sean
On 2/14/06, Manfred Geiler <ma...@gmail.com> wrote:
> Something like this should do it:
>
> <plugin>
> <artifactId>maven-antrun-plugin</artifactId>
> <executions>
> <execution>
> <phase>generate-sources</phase>
> <configuration>
> <tasks>
> <xslt basedir="src/main/tld"
> includes="*.tld"
> destdir="${project.build.directory}/tld"
> style="src/main/tld/misc/resolve_entities.xsl"
> extension=".tld">
> <xmlcatalog>
> <dtd publicid="-//Sun Microsystems, Inc.//DTD
> JSP Tag Library 1.2//EN"
> location="src/main/tld/misc"/>
> </xmlcatalog>
> </xslt>
> </tasks>
> </configuration>
> <goals>
> <goal>run</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
>
> Have not tried it yet. Perhaps I will have a chance to play around a
> little bit in the afternoon.
>
> Manfred
>
>
>
>
> On 2/14/06, Sean Schofield <se...@gmail.com> wrote:
> > > Maybe the maven-antrun-plugin can help until the xslt plugin is released.
> >
> > How so? To run an ant xslt task?
> >
> > > Bernd
> >
> > Sean
> >
>
Re: [maven] Issue with Core Release
Posted by Manfred Geiler <ma...@gmail.com>.
Something like this should do it:
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<phase>generate-sources</phase>
<configuration>
<tasks>
<xslt basedir="src/main/tld"
includes="*.tld"
destdir="${project.build.directory}/tld"
style="src/main/tld/misc/resolve_entities.xsl"
extension=".tld">
<xmlcatalog>
<dtd publicid="-//Sun Microsystems, Inc.//DTD
JSP Tag Library 1.2//EN"
location="src/main/tld/misc"/>
</xmlcatalog>
</xslt>
</tasks>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
</plugin>
Have not tried it yet. Perhaps I will have a chance to play around a
little bit in the afternoon.
Manfred
On 2/14/06, Sean Schofield <se...@gmail.com> wrote:
> > Maybe the maven-antrun-plugin can help until the xslt plugin is released.
>
> How so? To run an ant xslt task?
>
> > Bernd
>
> Sean
>
Re: [maven] Issue with Core Release
Posted by Sean Schofield <se...@gmail.com>.
> Maybe the maven-antrun-plugin can help until the xslt plugin is released.
How so? To run an ant xslt task?
> Bernd
Sean
Re: [maven] Issue with Core Release
Posted by Bernd Bohmann <be...@atanion.com>.
Maybe the maven-antrun-plugin can help until the xslt plugin is released.
Bernd
Sean Schofield schrieb:
> I manulally created the branch so we can begin testing the core. We
> still need to resolve the XSLT plugin issue before we release.
>
> Sean
>
> On 2/13/06, Manfred Geiler <ma...@gmail.com> wrote:
>
>>After a short offline discussion with Martin and some rethinking I
>>must admit that Bernd is absolutely right. So I will answer my
>>predication myself. ;-)
>>
>>What I did not take into account was the source assembly we release as
>>well. There is no guarantee that in a few weeks people will be able to
>>build proper binaries if one of the plugins that is part of the build
>>process is subject to change. So, no good idea to release with any
>>dependency on a SNAPSHOT artifact - be it plugin or not.
>>
>>Sorry for beeing slow-witted. :-)
>>
>>Manfred
>>
>>
>>
>>On 2/13/06, Manfred Geiler <ma...@gmail.com> wrote:
>>
>>>On 2/11/06, Bernd Bohmann <be...@atanion.com> wrote:
>>>
>>>>I would never allow to patch the release plugin to accept a SNAPSHOT
>>>>version. You don't need to use the final version you can use a released
>>>>version but never a SNAPSHOT.(The release version maybe a alpha or beta
>>>>release)
>>>
>>>Yes, I know what "SNAPSHOT" means for Maven. What we are speaking of
>>>here is a plugin not a lib that we rely on, right? Of course, I would
>>>never allow a MyFaces release with SNAPSHOT dependencies as well. But
>>>there is no real danger when we "convince" the release plugin to let
>>>us utilize something we would use anyway if we would release by hand.
>>>The release plugin is a convenient tool to make the process of
>>>releasing easier, right? So, nobody would stop us from releasing by
>>>hand even so the XSLT plugin is available only as a SNAPSHOT by now.
>>>Anyhow, I agree that convincing the XSLT plugin people to release an
>>>alpha version is the better and easier solution. Thanks, Sean.
>>>
>>>Manfred
>>>
>>>
>>>
>>>
>>>
>>>
>>>>Regards
>>>>
>>>>Bernd
>>>>
>>>>Manfred Geiler schrieb:
>>>>
>>>>>Yes, I agree with Martin.
>>>>>Perhaps a better way would be to patch the release plugin so that it
>>>>>accepts SNAPSHOTs. Since I have dived into maven this week for a
>>>>>rather complex project at my company, I'm no longer a total maven
>>>>>newby. Hope I can afford some time next week to bring in my new
>>>>>knowledge into MyFaces. As as starter I can have a look at the release
>>>>>plugin sourcecode and see what's possible - but not before monday.
>>>>>
>>>>>WDYT?
>>>>>
>>>>>Manfred
>>>>>
>>>>>
>>>>>On 2/11/06, Martin Marinschek <ma...@gmail.com> wrote:
>>>>>
>>>>>
>>>>>>I don't even see why you need to be forced to use the final version of
>>>>>>a plugin - you can have an alpha-state plugin doing something on a
>>>>>>very mature project.
>>>>>>
>>>>>>regards,
>>>>>>
>>>>>>Martin
>>>>>>
>>>>>>On 2/11/06, Sean Schofield <se...@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>>>I also posted about issue on the maven dev list. There is definitely
>>>>>>>room for improvement in the release plugin. It doesn't really
>>>>>>>envision you creating a branch for a release that will be down the
>>>>>>>road some time. I don't see why we need to switch to final versions
>>>>>>>of a plugin until we are actually ready to release. Of course we
>>>>>>>could skip the plugin but maven automates some of the important tasks
>>>>>>>for you.
>>>>>>>
>>>>>>>Sean
>>>>>>>
>>>>>>>On 2/11/06, Matthias Wessendorf <mw...@gmail.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>>>>The biggest issue is the XSLT plugin. That is a snapshot and its not
>>>>>>>>>a myfaces plugin. The only solution I can think of is to add it to
>>>>>>>>>the maven project as our own plugin and release it (with a myfaces
>>>>>>>>>group id.) Then when they finally get around to releasing the plugin
>>>>>>>>>we could switch to the official one.
>>>>>>>>
>>>>>>>>I am not that maven guy, but this kind of *work around* sounds ok for me.
>>>>>>>>
>>>>>>>>-Matthias
>>>>>>>>
>>>>>>>
>>>>>>--
>>>>>>
>>>>>>http://www.irian.at
>>>>>>
>>>>>>Your JSF powerhouse -
>>>>>>JSF Consulting, Development and
>>>>>>Courses in English and German
>>>>>>
>>>>>>Professional Support for Apache MyFaces
>>>>>>
>>>>>
>>>>>
>>>>--
>>>>Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development
>>>>Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com
>>>>phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333
>>>>
>>>
>
--
Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development
Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com
phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333
Re: [maven] Issue with Core Release
Posted by Sean Schofield <se...@gmail.com>.
I manulally created the branch so we can begin testing the core. We
still need to resolve the XSLT plugin issue before we release.
Sean
On 2/13/06, Manfred Geiler <ma...@gmail.com> wrote:
> After a short offline discussion with Martin and some rethinking I
> must admit that Bernd is absolutely right. So I will answer my
> predication myself. ;-)
>
> What I did not take into account was the source assembly we release as
> well. There is no guarantee that in a few weeks people will be able to
> build proper binaries if one of the plugins that is part of the build
> process is subject to change. So, no good idea to release with any
> dependency on a SNAPSHOT artifact - be it plugin or not.
>
> Sorry for beeing slow-witted. :-)
>
> Manfred
>
>
>
> On 2/13/06, Manfred Geiler <ma...@gmail.com> wrote:
> > On 2/11/06, Bernd Bohmann <be...@atanion.com> wrote:
> > > I would never allow to patch the release plugin to accept a SNAPSHOT
> > > version. You don't need to use the final version you can use a released
> > > version but never a SNAPSHOT.(The release version maybe a alpha or beta
> > > release)
> >
> > Yes, I know what "SNAPSHOT" means for Maven. What we are speaking of
> > here is a plugin not a lib that we rely on, right? Of course, I would
> > never allow a MyFaces release with SNAPSHOT dependencies as well. But
> > there is no real danger when we "convince" the release plugin to let
> > us utilize something we would use anyway if we would release by hand.
> > The release plugin is a convenient tool to make the process of
> > releasing easier, right? So, nobody would stop us from releasing by
> > hand even so the XSLT plugin is available only as a SNAPSHOT by now.
> > Anyhow, I agree that convincing the XSLT plugin people to release an
> > alpha version is the better and easier solution. Thanks, Sean.
> >
> > Manfred
> >
> >
> >
> >
> >
> > > Regards
> > >
> > > Bernd
> > >
> > > Manfred Geiler schrieb:
> > > > Yes, I agree with Martin.
> > > > Perhaps a better way would be to patch the release plugin so that it
> > > > accepts SNAPSHOTs. Since I have dived into maven this week for a
> > > > rather complex project at my company, I'm no longer a total maven
> > > > newby. Hope I can afford some time next week to bring in my new
> > > > knowledge into MyFaces. As as starter I can have a look at the release
> > > > plugin sourcecode and see what's possible - but not before monday.
> > > >
> > > > WDYT?
> > > >
> > > > Manfred
> > > >
> > > >
> > > > On 2/11/06, Martin Marinschek <ma...@gmail.com> wrote:
> > > >
> > > >>I don't even see why you need to be forced to use the final version of
> > > >>a plugin - you can have an alpha-state plugin doing something on a
> > > >>very mature project.
> > > >>
> > > >>regards,
> > > >>
> > > >>Martin
> > > >>
> > > >>On 2/11/06, Sean Schofield <se...@gmail.com> wrote:
> > > >>
> > > >>>I also posted about issue on the maven dev list. There is definitely
> > > >>>room for improvement in the release plugin. It doesn't really
> > > >>>envision you creating a branch for a release that will be down the
> > > >>>road some time. I don't see why we need to switch to final versions
> > > >>>of a plugin until we are actually ready to release. Of course we
> > > >>>could skip the plugin but maven automates some of the important tasks
> > > >>>for you.
> > > >>>
> > > >>>Sean
> > > >>>
> > > >>>On 2/11/06, Matthias Wessendorf <mw...@gmail.com> wrote:
> > > >>>
> > > >>>>>The biggest issue is the XSLT plugin. That is a snapshot and its not
> > > >>>>>a myfaces plugin. The only solution I can think of is to add it to
> > > >>>>>the maven project as our own plugin and release it (with a myfaces
> > > >>>>>group id.) Then when they finally get around to releasing the plugin
> > > >>>>>we could switch to the official one.
> > > >>>>
> > > >>>>I am not that maven guy, but this kind of *work around* sounds ok for me.
> > > >>>>
> > > >>>>-Matthias
> > > >>>>
> > > >>>
> > > >>
> > > >>--
> > > >>
> > > >>http://www.irian.at
> > > >>
> > > >>Your JSF powerhouse -
> > > >>JSF Consulting, Development and
> > > >>Courses in English and German
> > > >>
> > > >>Professional Support for Apache MyFaces
> > > >>
> > > >
> > > >
> > >
> > > --
> > > Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development
> > > Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com
> > > phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333
> > >
> >
>
Re: [maven] Issue with Core Release
Posted by Manfred Geiler <ma...@gmail.com>.
After a short offline discussion with Martin and some rethinking I
must admit that Bernd is absolutely right. So I will answer my
predication myself. ;-)
What I did not take into account was the source assembly we release as
well. There is no guarantee that in a few weeks people will be able to
build proper binaries if one of the plugins that is part of the build
process is subject to change. So, no good idea to release with any
dependency on a SNAPSHOT artifact - be it plugin or not.
Sorry for beeing slow-witted. :-)
Manfred
On 2/13/06, Manfred Geiler <ma...@gmail.com> wrote:
> On 2/11/06, Bernd Bohmann <be...@atanion.com> wrote:
> > I would never allow to patch the release plugin to accept a SNAPSHOT
> > version. You don't need to use the final version you can use a released
> > version but never a SNAPSHOT.(The release version maybe a alpha or beta
> > release)
>
> Yes, I know what "SNAPSHOT" means for Maven. What we are speaking of
> here is a plugin not a lib that we rely on, right? Of course, I would
> never allow a MyFaces release with SNAPSHOT dependencies as well. But
> there is no real danger when we "convince" the release plugin to let
> us utilize something we would use anyway if we would release by hand.
> The release plugin is a convenient tool to make the process of
> releasing easier, right? So, nobody would stop us from releasing by
> hand even so the XSLT plugin is available only as a SNAPSHOT by now.
> Anyhow, I agree that convincing the XSLT plugin people to release an
> alpha version is the better and easier solution. Thanks, Sean.
>
> Manfred
>
>
>
>
>
> > Regards
> >
> > Bernd
> >
> > Manfred Geiler schrieb:
> > > Yes, I agree with Martin.
> > > Perhaps a better way would be to patch the release plugin so that it
> > > accepts SNAPSHOTs. Since I have dived into maven this week for a
> > > rather complex project at my company, I'm no longer a total maven
> > > newby. Hope I can afford some time next week to bring in my new
> > > knowledge into MyFaces. As as starter I can have a look at the release
> > > plugin sourcecode and see what's possible - but not before monday.
> > >
> > > WDYT?
> > >
> > > Manfred
> > >
> > >
> > > On 2/11/06, Martin Marinschek <ma...@gmail.com> wrote:
> > >
> > >>I don't even see why you need to be forced to use the final version of
> > >>a plugin - you can have an alpha-state plugin doing something on a
> > >>very mature project.
> > >>
> > >>regards,
> > >>
> > >>Martin
> > >>
> > >>On 2/11/06, Sean Schofield <se...@gmail.com> wrote:
> > >>
> > >>>I also posted about issue on the maven dev list. There is definitely
> > >>>room for improvement in the release plugin. It doesn't really
> > >>>envision you creating a branch for a release that will be down the
> > >>>road some time. I don't see why we need to switch to final versions
> > >>>of a plugin until we are actually ready to release. Of course we
> > >>>could skip the plugin but maven automates some of the important tasks
> > >>>for you.
> > >>>
> > >>>Sean
> > >>>
> > >>>On 2/11/06, Matthias Wessendorf <mw...@gmail.com> wrote:
> > >>>
> > >>>>>The biggest issue is the XSLT plugin. That is a snapshot and its not
> > >>>>>a myfaces plugin. The only solution I can think of is to add it to
> > >>>>>the maven project as our own plugin and release it (with a myfaces
> > >>>>>group id.) Then when they finally get around to releasing the plugin
> > >>>>>we could switch to the official one.
> > >>>>
> > >>>>I am not that maven guy, but this kind of *work around* sounds ok for me.
> > >>>>
> > >>>>-Matthias
> > >>>>
> > >>>
> > >>
> > >>--
> > >>
> > >>http://www.irian.at
> > >>
> > >>Your JSF powerhouse -
> > >>JSF Consulting, Development and
> > >>Courses in English and German
> > >>
> > >>Professional Support for Apache MyFaces
> > >>
> > >
> > >
> >
> > --
> > Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development
> > Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com
> > phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333
> >
>
Re: [maven] Issue with Core Release
Posted by Manfred Geiler <ma...@gmail.com>.
On 2/11/06, Bernd Bohmann <be...@atanion.com> wrote:
> I would never allow to patch the release plugin to accept a SNAPSHOT
> version. You don't need to use the final version you can use a released
> version but never a SNAPSHOT.(The release version maybe a alpha or beta
> release)
Yes, I know what "SNAPSHOT" means for Maven. What we are speaking of
here is a plugin not a lib that we rely on, right? Of course, I would
never allow a MyFaces release with SNAPSHOT dependencies as well. But
there is no real danger when we "convince" the release plugin to let
us utilize something we would use anyway if we would release by hand.
The release plugin is a convenient tool to make the process of
releasing easier, right? So, nobody would stop us from releasing by
hand even so the XSLT plugin is available only as a SNAPSHOT by now.
Anyhow, I agree that convincing the XSLT plugin people to release an
alpha version is the better and easier solution. Thanks, Sean.
Manfred
> Regards
>
> Bernd
>
> Manfred Geiler schrieb:
> > Yes, I agree with Martin.
> > Perhaps a better way would be to patch the release plugin so that it
> > accepts SNAPSHOTs. Since I have dived into maven this week for a
> > rather complex project at my company, I'm no longer a total maven
> > newby. Hope I can afford some time next week to bring in my new
> > knowledge into MyFaces. As as starter I can have a look at the release
> > plugin sourcecode and see what's possible - but not before monday.
> >
> > WDYT?
> >
> > Manfred
> >
> >
> > On 2/11/06, Martin Marinschek <ma...@gmail.com> wrote:
> >
> >>I don't even see why you need to be forced to use the final version of
> >>a plugin - you can have an alpha-state plugin doing something on a
> >>very mature project.
> >>
> >>regards,
> >>
> >>Martin
> >>
> >>On 2/11/06, Sean Schofield <se...@gmail.com> wrote:
> >>
> >>>I also posted about issue on the maven dev list. There is definitely
> >>>room for improvement in the release plugin. It doesn't really
> >>>envision you creating a branch for a release that will be down the
> >>>road some time. I don't see why we need to switch to final versions
> >>>of a plugin until we are actually ready to release. Of course we
> >>>could skip the plugin but maven automates some of the important tasks
> >>>for you.
> >>>
> >>>Sean
> >>>
> >>>On 2/11/06, Matthias Wessendorf <mw...@gmail.com> wrote:
> >>>
> >>>>>The biggest issue is the XSLT plugin. That is a snapshot and its not
> >>>>>a myfaces plugin. The only solution I can think of is to add it to
> >>>>>the maven project as our own plugin and release it (with a myfaces
> >>>>>group id.) Then when they finally get around to releasing the plugin
> >>>>>we could switch to the official one.
> >>>>
> >>>>I am not that maven guy, but this kind of *work around* sounds ok for me.
> >>>>
> >>>>-Matthias
> >>>>
> >>>
> >>
> >>--
> >>
> >>http://www.irian.at
> >>
> >>Your JSF powerhouse -
> >>JSF Consulting, Development and
> >>Courses in English and German
> >>
> >>Professional Support for Apache MyFaces
> >>
> >
> >
>
> --
> Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development
> Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com
> phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333
>
Re: [maven] Issue with Core Release
Posted by Bernd Bohmann <be...@atanion.com>.
I would never allow to patch the release plugin to accept a SNAPSHOT
version. You don't need to use the final version you can use a released
version but never a SNAPSHOT.(The release version maybe a alpha or beta
release)
Regards
Bernd
Manfred Geiler schrieb:
> Yes, I agree with Martin.
> Perhaps a better way would be to patch the release plugin so that it
> accepts SNAPSHOTs. Since I have dived into maven this week for a
> rather complex project at my company, I'm no longer a total maven
> newby. Hope I can afford some time next week to bring in my new
> knowledge into MyFaces. As as starter I can have a look at the release
> plugin sourcecode and see what's possible - but not before monday.
>
> WDYT?
>
> Manfred
>
>
> On 2/11/06, Martin Marinschek <ma...@gmail.com> wrote:
>
>>I don't even see why you need to be forced to use the final version of
>>a plugin - you can have an alpha-state plugin doing something on a
>>very mature project.
>>
>>regards,
>>
>>Martin
>>
>>On 2/11/06, Sean Schofield <se...@gmail.com> wrote:
>>
>>>I also posted about issue on the maven dev list. There is definitely
>>>room for improvement in the release plugin. It doesn't really
>>>envision you creating a branch for a release that will be down the
>>>road some time. I don't see why we need to switch to final versions
>>>of a plugin until we are actually ready to release. Of course we
>>>could skip the plugin but maven automates some of the important tasks
>>>for you.
>>>
>>>Sean
>>>
>>>On 2/11/06, Matthias Wessendorf <mw...@gmail.com> wrote:
>>>
>>>>>The biggest issue is the XSLT plugin. That is a snapshot and its not
>>>>>a myfaces plugin. The only solution I can think of is to add it to
>>>>>the maven project as our own plugin and release it (with a myfaces
>>>>>group id.) Then when they finally get around to releasing the plugin
>>>>>we could switch to the official one.
>>>>
>>>>I am not that maven guy, but this kind of *work around* sounds ok for me.
>>>>
>>>>-Matthias
>>>>
>>>
>>
>>--
>>
>>http://www.irian.at
>>
>>Your JSF powerhouse -
>>JSF Consulting, Development and
>>Courses in English and German
>>
>>Professional Support for Apache MyFaces
>>
>
>
--
Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development
Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com
phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333
Re: [maven] Issue with Core Release
Posted by Manfred Geiler <ma...@gmail.com>.
Yes, I agree with Martin.
Perhaps a better way would be to patch the release plugin so that it
accepts SNAPSHOTs. Since I have dived into maven this week for a
rather complex project at my company, I'm no longer a total maven
newby. Hope I can afford some time next week to bring in my new
knowledge into MyFaces. As as starter I can have a look at the release
plugin sourcecode and see what's possible - but not before monday.
WDYT?
Manfred
On 2/11/06, Martin Marinschek <ma...@gmail.com> wrote:
> I don't even see why you need to be forced to use the final version of
> a plugin - you can have an alpha-state plugin doing something on a
> very mature project.
>
> regards,
>
> Martin
>
> On 2/11/06, Sean Schofield <se...@gmail.com> wrote:
> > I also posted about issue on the maven dev list. There is definitely
> > room for improvement in the release plugin. It doesn't really
> > envision you creating a branch for a release that will be down the
> > road some time. I don't see why we need to switch to final versions
> > of a plugin until we are actually ready to release. Of course we
> > could skip the plugin but maven automates some of the important tasks
> > for you.
> >
> > Sean
> >
> > On 2/11/06, Matthias Wessendorf <mw...@gmail.com> wrote:
> > > > The biggest issue is the XSLT plugin. That is a snapshot and its not
> > > > a myfaces plugin. The only solution I can think of is to add it to
> > > > the maven project as our own plugin and release it (with a myfaces
> > > > group id.) Then when they finally get around to releasing the plugin
> > > > we could switch to the official one.
> > >
> > > I am not that maven guy, but this kind of *work around* sounds ok for me.
> > >
> > > -Matthias
> > >
> >
>
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
Re: [maven] Issue with Core Release
Posted by Martin Marinschek <ma...@gmail.com>.
I don't even see why you need to be forced to use the final version of
a plugin - you can have an alpha-state plugin doing something on a
very mature project.
regards,
Martin
On 2/11/06, Sean Schofield <se...@gmail.com> wrote:
> I also posted about issue on the maven dev list. There is definitely
> room for improvement in the release plugin. It doesn't really
> envision you creating a branch for a release that will be down the
> road some time. I don't see why we need to switch to final versions
> of a plugin until we are actually ready to release. Of course we
> could skip the plugin but maven automates some of the important tasks
> for you.
>
> Sean
>
> On 2/11/06, Matthias Wessendorf <mw...@gmail.com> wrote:
> > > The biggest issue is the XSLT plugin. That is a snapshot and its not
> > > a myfaces plugin. The only solution I can think of is to add it to
> > > the maven project as our own plugin and release it (with a myfaces
> > > group id.) Then when they finally get around to releasing the plugin
> > > we could switch to the official one.
> >
> > I am not that maven guy, but this kind of *work around* sounds ok for me.
> >
> > -Matthias
> >
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: [maven] Issue with Core Release
Posted by Sean Schofield <se...@gmail.com>.
I also posted about issue on the maven dev list. There is definitely
room for improvement in the release plugin. It doesn't really
envision you creating a branch for a release that will be down the
road some time. I don't see why we need to switch to final versions
of a plugin until we are actually ready to release. Of course we
could skip the plugin but maven automates some of the important tasks
for you.
Sean
On 2/11/06, Matthias Wessendorf <mw...@gmail.com> wrote:
> > The biggest issue is the XSLT plugin. That is a snapshot and its not
> > a myfaces plugin. The only solution I can think of is to add it to
> > the maven project as our own plugin and release it (with a myfaces
> > group id.) Then when they finally get around to releasing the plugin
> > we could switch to the official one.
>
> I am not that maven guy, but this kind of *work around* sounds ok for me.
>
> -Matthias
>
Re: [maven] Issue with Core Release
Posted by Matthias Wessendorf <mw...@gmail.com>.
> The biggest issue is the XSLT plugin. That is a snapshot and its not
> a myfaces plugin. The only solution I can think of is to add it to
> the maven project as our own plugin and release it (with a myfaces
> group id.) Then when they finally get around to releasing the plugin
> we could switch to the official one.
I am not that maven guy, but this kind of *work around* sounds ok for me.
-Matthias