You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by wa...@wispertel.net on 2006/03/17 09:07:41 UTC
Maven2 Build Status
I have added some new capabilities to the Maven2 build. Here is an outline
of the current commands:
mvn clean
mvn -P [test][,min]
mvn -P tomcat,[test],[,min][,nodb]
mvn -P tomcat,hot,[test],[min]
where:
clean = clean build
test = build with component tests
min = minimum pages/portlet apps build
nodb = skip production db update
hot = hot deploy components, applications, or portal content
It is starting to get there... at last!
Randy
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Maven2 Build Status
Posted by David Sean Taylor <da...@bluesunrise.com>.
Dr. Michael Lipp wrote:
> Hi,
>
> just (carefully) asking: there was that poll recently about continuing
> to use maven or using ant and I admit that I have not really counted the
> results and I admit that I am biased, but I had the strong impression
> that it turned out to be in favour of ant.
>
> Now, I may have missed a summary posting (and searching for "maven ant"
> in the archive isn't really helpful), and I don't want to question
> anybody's work to get maven2 working, but I am a bit suprised about the
> continuing maven2 effort.
>
> Could anybody give me a hint?
We delayed voting pending the results of Randy's work. And it does look
very promising. As you can see, we are using Ant builds integrated with
Maven-2, so the solution does use Ant as well as Maven-2.
I suggest that you try it out, and let us know how it works for you
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Maven2 Build Status
Posted by "Dr. Michael Lipp" <Mi...@danet.de>.
Hi,
just (carefully) asking: there was that poll recently about continuing
to use maven or using ant and I admit that I have not really counted the
results and I admit that I am biased, but I had the strong impression
that it turned out to be in favour of ant.
Now, I may have missed a summary posting (and searching for "maven ant"
in the archive isn't really helpful), and I don't want to question
anybody's work to get maven2 working, but I am a bit suprised about the
continuing maven2 effort.
Could anybody give me a hint?
Regards,
Michael
watler@wispertel.net wrote:
> I have added some new capabilities to the Maven2 build. Here is an outline
> of the current commands:
>
> mvn clean
> mvn -P [test][,min]
> mvn -P tomcat,[test],[,min][,nodb]
> mvn -P tomcat,hot,[test],[min]
>
> where:
>
> clean = clean build
> test = build with component tests
> min = minimum pages/portlet apps build
> nodb = skip production db update
> hot = hot deploy components, applications, or portal content
>
> It is starting to get there... at last!
>
> Randy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
--
Dr. Michael N. Lipp
Solution Architect
Danet GmbH, Gutenbergstraße 10, 64331 Weiterstadt, Germany
Phone: +49 6151 868-476, Fax: +49 6151 868-264
eMail: Michael.Lipp@danet.de, URL: www.danet.com
-----------------------------------------------------------------------
Managing Board: Dr. Reiner Nickel (CEO), Dr. Burkhard Austermühl (CFO);
Chairman of the Supervisory Board: Jaques Bentz; Address of Record:
Weiterstadt; Commercial Register: Amtsgericht Darmstadt HRB 6450;
Tax Number: DE 172 993 071
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Maven2 Build Status
Posted by Randy Watler <wa...@wispertel.net>.
Brett,
Thanks for your continued interest in getting Maven2 up and running on
Jetspeed2. See inline comments below...
On Sat, 2006-03-18 at 21:00 +1100, Brett Porter wrote:
> Hi Randy,
>
> I was pointed at your previous Maven2 discussions and asked to help
> out where I can.
>
> I have a couple of thoughts:
>
> On 3/18/06, Randy Watler <wa...@wispertel.net> wrote:
> > For the Maven2 based genapp approach, I am planning to use a Maven2
> > archetype to do most of the heavy lifting at first. Once again, this
> > will be Ant based under the Maven2 build.
>
> Would it help if we added the archetype creation to our ant tasks?
> Remember, Maven plugins are designed to be easily wrapped as ant
> tasks, so we can do that for the archetype plugin goals if needed.
This may indeed be helpful, but I am not quite ready to answer yet. Once
I have the archetypes developed and we are happy with that approach, it
is likely that our Ant user community would like to see such a thing. I
am already making heavy use of the Maven2 Artifact Ant library, so
relying on another Maven Ant task would not pose an issue. There is also
a chance that the number of properties that need to be supplied to the
archetype generation are small and that we may be able to use some
simple Ant replace tasks to customize a downloaded pre-expanded
archetype. Not sure yet there... but I am very certain that we will need
to provide a downloadable repository to help first time users get
bootstrapped in the Ant environment. We will also be maintaining a
Jetspeed specific repository graciously hosted by BlueSunrise to help
insulate Jetspeed users from POM issues that crop up occasionally in the
central repository.
>
> > Finally, I have to say that there are bugs in Maven2 that are making
> > this whole process harder than it should be. I plan on working with the
> > Maven2 team, just as many of you work with us, to resolve them as best I
> > can.
>
> Happy to help - just point out the issues you file so that we can give
> them some priority.
I will certainly do that. I have not run into any showstoppers yet, but
there have been some things that have taken me some time to figure out.
Overall, I am satisfied with Maven2 and its ability to support
Jetspeed's build requirements. You guys have also been great on IRC...
thanks for the help.
I would be very interested in having you guys review the Jetspeed Maven2
build once it is complete. I am not sure that I have made the best
choices along the way, and could use some mentoring. At the moment, the
Maven2 build is setup alongside the Maven1 build and is available in the
Jetspeed 2.1-dev SVN trunk.
Thanks again,
Randy
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Maven2 Build Status
Posted by Brett Porter <br...@gmail.com>.
Hi Randy,
I was pointed at your previous Maven2 discussions and asked to help
out where I can.
I have a couple of thoughts:
On 3/18/06, Randy Watler <wa...@wispertel.net> wrote:
> For the Maven2 based genapp approach, I am planning to use a Maven2
> archetype to do most of the heavy lifting at first. Once again, this
> will be Ant based under the Maven2 build.
Would it help if we added the archetype creation to our ant tasks?
Remember, Maven plugins are designed to be easily wrapped as ant
tasks, so we can do that for the archetype plugin goals if needed.
> Finally, I have to say that there are bugs in Maven2 that are making
> this whole process harder than it should be. I plan on working with the
> Maven2 team, just as many of you work with us, to resolve them as best I
> can.
Happy to help - just point out the issues you file so that we can give
them some priority.
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Maven2 Build Status
Posted by Randy Watler <wa...@wispertel.net>.
Michael,
I understand your desire to make that broader statement. There are
bootstrapping issues at the boundary between Ant and Maven. The Maven
team has offered to potentially make it possible to avoid running Maven
by including the ability to expand maven archetypes in the Maven Ant
task library. However, Maven will still be there under hood. If you are
expecting Maven to be eradicated absolutely from the J2 build, that will
have to come later with a binary install.
Randy
On Mon, 2006-03-20 at 09:32 +0100, Dr. Michael Lipp wrote:
> Hi Randy,
>
> > 4. Produce binary distributions that ease the pain associated with the
> > Maven remote repository based solutions, (e.g. make a populated maven
> > repository available for download).
>
> Couldn't you make that: "Produce binary distributions that do not
> require maven[12]"?
>
> - Michael
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Maven2 Build Status
Posted by "Dr. Michael Lipp" <Mi...@danet.de>.
Hi Randy,
> 4. Produce binary distributions that ease the pain associated with the
> Maven remote repository based solutions, (e.g. make a populated maven
> repository available for download).
Couldn't you make that: "Produce binary distributions that do not
require maven[12]"?
- Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Maven2 Build Status
Posted by Randy Watler <wa...@wispertel.net>.
David/Michael,
These are all baby steps along the way to these goals:
0. Support Maven1 while developing new build solution.
1. Continue to support Maven, (in particular Maven2), for internal
builds as is being done by many Apache projects.
2. Avoid ANY plugin based code in favor of Ant build customizations.
3. Create a genapp solution that can be used by BOTH Maven2 and Ant
centric folk.
4. Produce binary distributions that ease the pain associated with the
Maven remote repository based solutions, (e.g. make a populated maven
repository available for download).
5. Create a 100% Ant genapp environment based on the same Ant scripts
the Maven2 build uses.
So, in a nutshell, I am basically reimplementing the existing plugin in
Ant. To do this, I am using the Maven2 Ant Artifact task library. Maven2
does most of the compiling and artifact creation, but Ant does all of
the things J2 implementors might need to do. At this point, the Ant
tasks that are part of the build are skewed toward the needs of Maven2,
but that will be changing in the next few days: my current focus is J2
genapp.
For the Maven2 based genapp approach, I am planning to use a Maven2
archetype to do most of the heavy lifting at first. Once again, this
will be Ant based under the Maven2 build. After we are satisfied that
the Maven2 aspects of genapp are decided, I will then include an Ant
main build script that takes the place of Maven2. Then, the only
question that remains is how to instantiate that environment.
I am not sure how to address the downloads yet. We will either continue
to use Maven2's repository, deliver a repository download, or rely on
the traditional and lib directory approach.
While our users clearly want an Ant option of some form and I am
attempting to answer the bell in that ring, the development community is
willing to give Maven2 a chance. I believe that there is quite a bit of
power in the Maven2+Ant approach. In fact, one can even write Ant
plugins in Maven2. I am steering clear of this for now as a concession
to the Ant community within J2. It does, however, demonstrate the fact
that Maven2 and Ant can be symbiotic technologies.
Finally, I have to say that there are bugs in Maven2 that are making
this whole process harder than it should be. I plan on working with the
Maven2 team, just as many of you work with us, to resolve them as best I
can. In the process, I expect the Maven2 configurations to be in a bit
of flux. However, the Ant work I am going to try to preserve in the
process. It really represents the bulk of the work here, so please
understand that this IS a vote for Ant!
Randy
On Fri, 2006-03-17 at 09:55 -0800, David Sean Taylor wrote:
> watler@wispertel.net wrote:
> > I have added some new capabilities to the Maven2 build. Here is an outline
> > of the current commands:
> >
> > mvn clean
> > mvn -P [test][,min]
> > mvn -P tomcat,[test],[,min][,nodb]
> > mvn -P tomcat,hot,[test],[min]
> >
> > where:
> >
> > clean = clean build
> > test = build with component tests
> > min = minimum pages/portlet apps build
> > nodb = skip production db update
> > hot = hot deploy components, applications, or portal content
> >
> > It is starting to get there... at last!
> >
> > Randy
> >
> Excellent! Looks very straight forward and easy to understand.
> I like that there is a specific deployment profile for Tomcat.
> The Maven-1 build was Tomcat-centric.
> We can later write profiles for Geronimo, Jetty...very cool.
>
> IMO, we need to support the 'genapp' use case, because that is what we
> all use with Maven-1 to configure and maintain a customized portal.
>
> Could you briefly explain how Maven-2 can be applied to solve the
> genapp use case?
> Also, if users want to use Ant to genapp, would that be possible?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Maven2 Build Status
Posted by Ralph Goers <Ra...@dslextreme.com>.
I hate to even ask this, but what is the chance of getting a deployment
for JBoss?
Ralph
David Sean Taylor wrote:
> watler@wispertel.net wrote:
>> I have added some new capabilities to the Maven2 build. Here is an
>> outline
>> of the current commands:
>>
>> mvn clean
>> mvn -P [test][,min]
>> mvn -P tomcat,[test],[,min][,nodb]
>> mvn -P tomcat,hot,[test],[min]
>>
>> where:
>>
>> clean = clean build
>> test = build with component tests
>> min = minimum pages/portlet apps build
>> nodb = skip production db update
>> hot = hot deploy components, applications, or portal content
>>
>> It is starting to get there... at last!
>>
>> Randy
>>
> Excellent! Looks very straight forward and easy to understand.
> I like that there is a specific deployment profile for Tomcat.
> The Maven-1 build was Tomcat-centric.
> We can later write profiles for Geronimo, Jetty...very cool.
>
> IMO, we need to support the 'genapp' use case, because that is what we
> all use with Maven-1 to configure and maintain a customized portal.
>
> Could you briefly explain how Maven-2 can be applied to solve the
> genapp use case?
> Also, if users want to use Ant to genapp, would that be possible?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: Maven2 Build Status
Posted by David Sean Taylor <da...@bluesunrise.com>.
watler@wispertel.net wrote:
> I have added some new capabilities to the Maven2 build. Here is an outline
> of the current commands:
>
> mvn clean
> mvn -P [test][,min]
> mvn -P tomcat,[test],[,min][,nodb]
> mvn -P tomcat,hot,[test],[min]
>
> where:
>
> clean = clean build
> test = build with component tests
> min = minimum pages/portlet apps build
> nodb = skip production db update
> hot = hot deploy components, applications, or portal content
>
> It is starting to get there... at last!
>
> Randy
>
Excellent! Looks very straight forward and easy to understand.
I like that there is a specific deployment profile for Tomcat.
The Maven-1 build was Tomcat-centric.
We can later write profiles for Geronimo, Jetty...very cool.
IMO, we need to support the 'genapp' use case, because that is what we
all use with Maven-1 to configure and maintain a customized portal.
Could you briefly explain how Maven-2 can be applied to solve the
genapp use case?
Also, if users want to use Ant to genapp, would that be possible?
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org