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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> wrote:
On 2/11/06, Bernd Bohmann <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
