You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Ron Wheeler <rw...@artifact-software.com> on 2005/10/20 16:43:43 UTC
Error buildinng M3 in Eclipse.
I am trying to build the M3 release in Eclipse (I have spent a lot of
time on the M4 release but it always seems to have a different bug each
week)
These are the steps that I have followed so far.
1) Create a new Eclipse
Maven project New=>Project=>Maven Project
Version is 3 (Do not know why)
2) Modify Maven Preferences to make the Eclipse workspace the Maven
Local Home
This seems to put the cache under the Eclipse project.
3)Run the Maven plug-in download to get the jetspeed plug-in for the
version of jetspeed required
maven -DartifactId=maven-jetspeed2-plugin -DgroupId=jetspeed2
-Dversion=2.0-M3 plugin:download
becomes
a run of the plugin:download task with 3 arguments(keys)
artifactId maven-jetspeed2-plugin
groupId jetspeed2
version 2.0-M3
This seems to work but when I try to run the jetspeed2: build.portal I
get the following output.
---------------------------------------------------------------------------------------------
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
build:start:
jetspeed2:build.portal:
[copy] Copying 8 files to
C:\eclipse\workspace\myJetspeed\etc\project-dependencies
[copy] Copying 2 files to
C:\eclipse\workspace\myJetspeed\etc\project-resources
[copy] Copying 1 file to
C:\eclipse\workspace\myJetspeed\etc\project-reports
[copy] Copying 1 file to C:\eclipse\workspace\myJetspeed
[copy] Copying 1 file to C:\eclipse\workspace\myJetspeed
BUILD FAILED
File......
C:\eclipse\workspace\myJetspeed\cache\maven-jetspeed2-plugin-2.0-M3\plugin.jelly
Element... maven:pom
Line...... 165
Column.... 86
Error parsing project.xml
'C:\eclipse\workspace\myJetspeed\cache\maven-jetspeed2-plugin-2.0-M3\plugin-resources\portal_project.xml'
Total time: 4 seconds
Finished at: Thu Oct 20 02:14:33 EDT 2005
----------------------------------------------------------------------------------------------------------
The portal_project.xml file seems to be well formed.
Is is possible that I am missing definitions in my build.properties that
M3 needs?
My build.properties contains the following:
maven.repo.remote = http://www.bluesunrise.com/maven/,
http://www.ibiblio.org/maven/, http://dist.codehaus.org/,
http://cvs.apache.org/repository
# jetspeed 2 home required for build
org.apache.jetspeed.project.home = c:/eclipse/workspace/myJetspeed
org.apache.jetspeed.groupId=jetspeedProjects
org.apache.jetspeed.artifactIDId=myJetspeed
org.apache.jetspeed.name=My Test Portal
org.apache.jetspeed.currentVersion=1.0
# jetspeed required properties
org.apache.jetspeed.server.home = c:/tomcat
org.apache.jetspeed.catalina.version.major = 5.5
org.apache.jetspeed.server.shared =
${org.apache.jetspeed.server.home}/shared/lib
org.apache.jetspeed.deploy.war.dir =
${org.apache.jetspeed.server.home}/webapps
org.apache.jetspeed.services.autodeployment.user = xxx
org.apache.jetspeed.services.autodeployment.password = yyy
org.apache.jetspeed.portal.name=myjetspeed
jetspeed.version=2.0-M3
# j2:portal.genapp properties
org.apache.jetspeed.genapp.home= c:/eclipse/workspace/myjetspeed
org.apache.jetspeed.genapp.groupId=myJetspeed
org.apache.jetspeed.genapp.name=My Test Portal
org.apache.jetspeed.genapp.currentVersion=1.0
# configure MySQL Test DB
# -------------------------------------------------------------------------
Omitted since it is likely not relevant at tyhis point
# -------------------------------------------------------------------------
# configure MySQL Production DB
# -------------------------------------------------------------------------
Ommitted
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Error buildinng M3 in Eclipse.
Posted by David Sean Taylor <da...@bluesunrise.com>.
Ron Wheeler wrote:
> David Sean Taylor wrote:
> <quote>
> The idea is that you don't need to download the Jetspeed source code to
> build your project. We want you to create a custom Jetspeed project as
> outlined in the Getting Started. I've found though, people often
> download the source anyway, and use it to learn from, extend, debug
> </quote>
>
> If the "Getting started" worked, I would have been happy. That is what I
> was trying to do originally but it did not work. Probably because of a
> problem (missing file) with the M4-SNAPSHOT.
>
> I think that the "Getting Started" needs a bit of work. It is probably
> not too far off but a recipe with one missing ingredient or step will
> not likely work in cooking or computering.
>
> 1) Separate out the building from source so that it is a separate
> procedure.
> 2) Test the "Geting Started" to make sure that it works. This should be
> done by at least 2 people working together. One person who knows how it
> should work and one person who is unfamiliar with the system but should
> be able to build an Jetspeed application.
>
> If there is anyone who knows who wants to work with me as the talented
> ignoramous, I would be willing to spend some time to get a decent
> "Getting Started" that works for most people.
>
Sure, contact me directly so we can agree on a time to work on it over IRC.
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Error buildinng M3 in Eclipse.
Posted by Ron Wheeler <rw...@artifact-software.com>.
David Sean Taylor wrote:
<quote>
The idea is that you don't need to download the Jetspeed source code to
build your project. We want you to create a custom Jetspeed project as
outlined in the Getting Started. I've found though, people often
download the source anyway, and use it to learn from, extend, debug
</quote>
If the "Getting started" worked, I would have been happy. That is what I
was trying to do originally but it did not work. Probably because of a
problem (missing file) with the M4-SNAPSHOT.
I think that the "Getting Started" needs a bit of work. It is probably
not too far off but a recipe with one missing ingredient or step will
not likely work in cooking or computering.
1) Separate out the building from source so that it is a separate
procedure.
2) Test the "Geting Started" to make sure that it works. This should be
done by at least 2 people working together. One person who knows how it
should work and one person who is unfamiliar with the system but should
be able to build an Jetspeed application.
If there is anyone who knows who wants to work with me as the talented
ignoramous, I would be willing to spend some time to get a decent
"Getting Started" that works for most people.
Ron
David Sean Taylor wrote:
> Ron Wheeler wrote:
>
>> Eclipse and Mavenide seem to have trouble letting go of things, so
>> deletes sometimes fail. goals.cache seems to be a regular problem.
>> Shutting down Eclipse is the only solution that I have come up with
>> for deleteing it under Windows.
>>
>> I have gotten pretty brutal with cleaning out things. I just shut
>> down Eclipse and delete everything under the {user_home}.maven
>> directory and clean out most of the stuff under my Eclipse project.
>>
> After my recent (and similar to yours) experiences with Mevenide, I
> won't be using it again anytime soon. Perhaps if you always build from
> within Eclipse there will be less errors. I don't.
>
>> I would like to get Eclipse, Maven and Jetspeed working properly. It
>> seems a bit non-deterministic but perhaps this is a combination of my
>> ignorance (not helped by the documentation) and maven/mavenide's
>> treatment of the cache.
>
>
> Have you looked here:
>
> http://maven.apache.org/reference/plugins/eclipse/goals.html
>
> you can run
>
> maven -o eclipse:external-tools
>
> but i didn't have much luck with Eclipse 3
>
> You can always configure Maven as an external tool
> Thats easy enough
>
> Also tried
>
> maven ant
>
> but it didn't generate what i expected
>
> Need to find time to try out Maven 2, or maybe Maven 1.1
> You're right though, Eclipse integration is lacking
>
> A basic portlet.xml editor and portlet deployer for Jetspeed would be
> great
>
>>
>> I am trying to figure out how to organize a portal project using
>> Jetspeed2. One of the temporary issues is that there are 2 projects
>> running separately but mixed together; The jakarta-jetspeed team has
>> a development project running and I have (or will have) a portal to
>> build. We both want to use the project structure to describe our
>> projects and I will likely need to add some goals to merge my
>> customizations to each new version of Jetspeed.
>
>
> The idea is that you don't need to download the Jetspeed source code
> to build your project. We want you to create a custom Jetspeed project
> as outlined in the Getting Started. I've found though, people often
> download the source anyway, and use it to learn from, extend, debug
>
>>
>> Has anyone given any thought about how web application developers
>> should work with Jetspeed under Eclipse?
>> What are you advising people who are trying to get started with
>> Jetspeed?
>>
>
> As you can see on website's Getting Started page, we are advising
> building with Maven.
> I have been traveling recently, teaching developers how to build with
> Jetspeed and Maven. Overall its been a rough experience.
> Its a challenge for people to get it to build. Once its working, it
> seems to go fine, but the initial experience is generally not pleasant.
> Developers want to build from Eclipse, not from the command line.
> There are a of lot build.properties parameters that are often
> mis-entered. I have installed Mevenide for some developers, and it
> seems to work fine for them. I think one problem is that I personally
> don't build from Eclipse, and in general prefer building from a shell.
>
> For better acceptance, I'd like to see Jetspeed and portlet.xml
> specific Eclipse plugins.
> I wrote a spec a Jetspeed Eclipse plugin once...
>
>> The documentation is probably about 80% complete but that still
>> leaves a lot out that is required to make Jetspeed useable. It
>> probably would not take too much to fill in the missing bits but it
>> seems that everyone has the same problems trying to follow what is
>> written. Some of it is really vague and, in places, contradictory.
>> From the errors that I am getting currently, I suspect that there
>> are bits and pieces of the maven stuff missing from the instructions
>> so that the defaults are not correct for running under Eclipse.
>
>
> We're open to suggestions on how to better improve the developer build
> experience. Im certainly eager to find better ways
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Eclipse as a development tools for Jetspeed.
Posted by Ron Wheeler <rw...@artifact-software.com>.
I do not have any experience with Maven so I am not sure if the problems
with Eclipse, Maven and Jetspeed are design flaws in one of the
components or is just my inexperience.
We use Eclipse for all of our other activities, from Actionscript
programming to controlling marketing documents.
It makes it easy to give non-programmers an easy to understand file
sharing system. We are not properly using all of its capabilities in
terms of versioning but we will get there.
I would like to use Eclipse with Jetspeed and have had some suggestions
given to me about how to organize the Jetspeed core with my own
customized elements.
1) I think that Ant/Maven could be very helpful in writing a build
process that takes our custom stuff and merges it with the "standard"
Jetspeed distribution to produce our portal. It would be nice if this
procedure could be set up so that new versions of Jetspeed2 could be
easily implemented into a running portal build.
2) There are lots of editors available for XML files in Eclipse and it
should be easy to build new editors for some of the Jetspeed file types,
using the tool kit that comes with Eclipse so that things like coloring
, code folding, outlines, etc. are quickly made available in a Jetspeed
plugin. The Flash Actionscript area just took off after many of us
adopted Eclipse as a coding platform. There are a lot of tools for
Eclipse being released and the tools are getting better each month. It
worked so well that Macromedia has built their next development IDE for
Flex around Eclipse. On the downside for Macromedia, Eclipse has reduced
the number of Flash licenses required for RIA design shops. You still
need 1 but each programmer only has to have Eclipse and the free tools.
I can see the same thing happening for Jetspeed if an Eclipse
environment can be created that makes it easy to manage the
customization of the portal.
In Maven, the j2 and Jetspeed goals are a bit confusing. Whey are there
2 separate sets of goals?
<rant>
Is it illegal for Jetspeed developers to add comments to their code? A
few comments in the XML files would go a long way to making the system
easier to work with. Even if the documentation is not going to be
written, the code at least should be documented. Maven/Ant goals should
have a description that makes sense. This might also prevent Jetspeed
developers from stepping on each other.
</rant>
The Maven Project structure for a portal designer is quite different
than the structure for the Jetspeed development team. The packaging and
installation instructions for distribution to portal developers needs to
take this into account.
If anyone in the Jetspeed team wants to work on this, I would be happy
to help. You bring the knowledge, I will provide the ignorance.
Ron
David Sean Taylor wrote:
> Ron Wheeler wrote:
>
>> Eclipse and Mavenide seem to have trouble letting go of things, so
>> deletes sometimes fail. goals.cache seems to be a regular problem.
>> Shutting down Eclipse is the only solution that I have come up with
>> for deleteing it under Windows.
>>
>> I have gotten pretty brutal with cleaning out things. I just shut
>> down Eclipse and delete everything under the {user_home}.maven
>> directory and clean out most of the stuff under my Eclipse project.
>>
> After my recent (and similar to yours) experiences with Mevenide, I
> won't be using it again anytime soon. Perhaps if you always build from
> within Eclipse there will be less errors. I don't.
>
>> I would like to get Eclipse, Maven and Jetspeed working properly. It
>> seems a bit non-deterministic but perhaps this is a combination of my
>> ignorance (not helped by the documentation) and maven/mavenide's
>> treatment of the cache.
>
>
> Have you looked here:
>
> http://maven.apache.org/reference/plugins/eclipse/goals.html
>
> you can run
>
> maven -o eclipse:external-tools
>
> but i didn't have much luck with Eclipse 3
>
> You can always configure Maven as an external tool
> Thats easy enough
>
> Also tried
>
> maven ant
>
> but it didn't generate what i expected
>
> Need to find time to try out Maven 2, or maybe Maven 1.1
> You're right though, Eclipse integration is lacking
>
> A basic portlet.xml editor and portlet deployer for Jetspeed would be
> great
>
>>
>> I am trying to figure out how to organize a portal project using
>> Jetspeed2. One of the temporary issues is that there are 2 projects
>> running separately but mixed together; The jakarta-jetspeed team has
>> a development project running and I have (or will have) a portal to
>> build. We both want to use the project structure to describe our
>> projects and I will likely need to add some goals to merge my
>> customizations to each new version of Jetspeed.
>
>
> The idea is that you don't need to download the Jetspeed source code
> to build your project. We want you to create a custom Jetspeed project
> as outlined in the Getting Started. I've found though, people often
> download the source anyway, and use it to learn from, extend, debug
>
>>
>> Has anyone given any thought about how web application developers
>> should work with Jetspeed under Eclipse?
>> What are you advising people who are trying to get started with
>> Jetspeed?
>>
>
> As you can see on website's Getting Started page, we are advising
> building with Maven.
> I have been traveling recently, teaching developers how to build with
> Jetspeed and Maven. Overall its been a rough experience.
> Its a challenge for people to get it to build. Once its working, it
> seems to go fine, but the initial experience is generally not pleasant.
> Developers want to build from Eclipse, not from the command line.
> There are a of lot build.properties parameters that are often
> mis-entered. I have installed Mevenide for some developers, and it
> seems to work fine for them. I think one problem is that I personally
> don't build from Eclipse, and in general prefer building from a shell.
>
> For better acceptance, I'd like to see Jetspeed and portlet.xml
> specific Eclipse plugins.
> I wrote a spec a Jetspeed Eclipse plugin once...
>
>> The documentation is probably about 80% complete but that still
>> leaves a lot out that is required to make Jetspeed useable. It
>> probably would not take too much to fill in the missing bits but it
>> seems that everyone has the same problems trying to follow what is
>> written. Some of it is really vague and, in places, contradictory.
>> From the errors that I am getting currently, I suspect that there
>> are bits and pieces of the maven stuff missing from the instructions
>> so that the defaults are not correct for running under Eclipse.
>
>
> We're open to suggestions on how to better improve the developer build
> experience. Im certainly eager to find better ways
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Error buildinng M3 in Eclipse.
Posted by David Sean Taylor <da...@bluesunrise.com>.
Ron Wheeler wrote:
> Eclipse and Mavenide seem to have trouble letting go of things, so
> deletes sometimes fail. goals.cache seems to be a regular problem.
> Shutting down Eclipse is the only solution that I have come up with for
> deleteing it under Windows.
>
> I have gotten pretty brutal with cleaning out things. I just shut down
> Eclipse and delete everything under the {user_home}.maven directory and
> clean out most of the stuff under my Eclipse project.
>
After my recent (and similar to yours) experiences with Mevenide, I
won't be using it again anytime soon. Perhaps if you always build from
within Eclipse there will be less errors. I don't.
> I would like to get Eclipse, Maven and Jetspeed working properly. It
> seems a bit non-deterministic but perhaps this is a combination of my
> ignorance (not helped by the documentation) and maven/mavenide's
> treatment of the cache.
Have you looked here:
http://maven.apache.org/reference/plugins/eclipse/goals.html
you can run
maven -o eclipse:external-tools
but i didn't have much luck with Eclipse 3
You can always configure Maven as an external tool
Thats easy enough
Also tried
maven ant
but it didn't generate what i expected
Need to find time to try out Maven 2, or maybe Maven 1.1
You're right though, Eclipse integration is lacking
A basic portlet.xml editor and portlet deployer for Jetspeed would be great
>
> I am trying to figure out how to organize a portal project using
> Jetspeed2. One of the temporary issues is that there are 2 projects
> running separately but mixed together; The jakarta-jetspeed team has a
> development project running and I have (or will have) a portal to build.
> We both want to use the project structure to describe our projects and I
> will likely need to add some goals to merge my customizations to each
> new version of Jetspeed.
The idea is that you don't need to download the Jetspeed source code to
build your project. We want you to create a custom Jetspeed project as
outlined in the Getting Started. I've found though, people often
download the source anyway, and use it to learn from, extend, debug
>
> Has anyone given any thought about how web application developers should
> work with Jetspeed under Eclipse?
> What are you advising people who are trying to get started with Jetspeed?
>
As you can see on website's Getting Started page, we are advising
building with Maven.
I have been traveling recently, teaching developers how to build with
Jetspeed and Maven. Overall its been a rough experience.
Its a challenge for people to get it to build. Once its working, it
seems to go fine, but the initial experience is generally not pleasant.
Developers want to build from Eclipse, not from the command line. There
are a of lot build.properties parameters that are often mis-entered. I
have installed Mevenide for some developers, and it seems to work fine
for them. I think one problem is that I personally don't build from
Eclipse, and in general prefer building from a shell.
For better acceptance, I'd like to see Jetspeed and portlet.xml specific
Eclipse plugins.
I wrote a spec a Jetspeed Eclipse plugin once...
> The documentation is probably about 80% complete but that still leaves a
> lot out that is required to make Jetspeed useable. It probably would not
> take too much to fill in the missing bits but it seems that everyone has
> the same problems trying to follow what is written. Some of it is really
> vague and, in places, contradictory.
> From the errors that I am getting currently, I suspect that there are
> bits and pieces of the maven stuff missing from the instructions so that
> the defaults are not correct for running under Eclipse.
We're open to suggestions on how to better improve the developer build
experience. Im certainly eager to find better ways
--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
[office] +01 707 773-4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Error buildinng M3 in Eclipse.
Posted by Ron Wheeler <rw...@artifact-software.com>.
Eclipse and Mavenide seem to have trouble letting go of things, so
deletes sometimes fail. goals.cache seems to be a regular problem.
Shutting down Eclipse is the only solution that I have come up with for
deleteing it under Windows.
I have gotten pretty brutal with cleaning out things. I just shut down
Eclipse and delete everything under the {user_home}.maven directory and
clean out most of the stuff under my Eclipse project.
I would like to get Eclipse, Maven and Jetspeed working properly. It
seems a bit non-deterministic but perhaps this is a combination of my
ignorance (not helped by the documentation) and maven/mavenide's
treatment of the cache.
I am trying to figure out how to organize a portal project using
Jetspeed2. One of the temporary issues is that there are 2 projects
running separately but mixed together; The jakarta-jetspeed team has a
development project running and I have (or will have) a portal to build.
We both want to use the project structure to describe our projects and I
will likely need to add some goals to merge my customizations to each
new version of Jetspeed.
Has anyone given any thought about how web application developers should
work with Jetspeed under Eclipse?
What are you advising people who are trying to get started with Jetspeed?
The documentation is probably about 80% complete but that still leaves a
lot out that is required to make Jetspeed useable. It probably would not
take too much to fill in the missing bits but it seems that everyone has
the same problems trying to follow what is written. Some of it is really
vague and, in places, contradictory.
From the errors that I am getting currently, I suspect that there are
bits and pieces of the maven stuff missing from the instructions so that
the defaults are not correct for running under Eclipse.
Ron
David Sean Taylor wrote:
>
> Ron Wheeler wrote:
>
>> I am trying to build the M3 release in Eclipse (I have spent a lot
>> of time on the M4 release but it always seems to have a different bug
>> each week)
>> These are the steps that I have followed so far.
>>
>> 1) Create a new Eclipse
>> Maven project New=>Project=>Maven Project
>> Version is 3 (Do not know why)
>>
>> 2) Modify Maven Preferences to make the Eclipse workspace the Maven
>> Local Home
>> This seems to put the cache under the Eclipse project.
>>
>> 3)Run the Maven plug-in download to get the jetspeed plug-in for the
>> version of jetspeed required
>> maven -DartifactId=maven-jetspeed2-plugin -DgroupId=jetspeed2
>> -Dversion=2.0-M3 plugin:download
>> becomes
>> a run of the plugin:download task with 3 arguments(keys)
>> artifactId maven-jetspeed2-plugin
>> groupId jetspeed2
>> version 2.0-M3
>>
>> This seems to work but when I try to run the jetspeed2: build.portal
>> I get the following output.
>>
> Note, Ive stopped using the Maven plugin for Eclipse. It was causing
> me lots of problems with my Maven cache.
>
> If you have previously built with M4, recommend cleaning out all Maven
> caches such as:
>
> rm $MAVEN_HOME/plugins/maven-jetspeed2*.jar
> rm
> $HOME/.maven/repository/jetspeed2/plugins/maven-jetspeed2-plugin-2.0-M4-SNAPSHOT.jar
>
>
> rm -R $HOME/.maven/plugins/maven-jetspeed2-plugin-2.0-M4-SNAPSHOT
> rm -R $HOME/.maven/cache/maven-jetspeed2-plugin-2.0-M4-SNAPSHOT
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Error buildinng M3 in Eclipse.
Posted by David Sean Taylor <da...@bluesunrise.com>.
Ron Wheeler wrote:
> I am trying to build the M3 release in Eclipse (I have spent a lot of
> time on the M4 release but it always seems to have a different bug each
> week)
> These are the steps that I have followed so far.
>
> 1) Create a new Eclipse
> Maven project New=>Project=>Maven Project
> Version is 3 (Do not know why)
>
> 2) Modify Maven Preferences to make the Eclipse workspace the Maven
> Local Home
> This seems to put the cache under the Eclipse project.
>
> 3)Run the Maven plug-in download to get the jetspeed plug-in for the
> version of jetspeed required
> maven -DartifactId=maven-jetspeed2-plugin -DgroupId=jetspeed2
> -Dversion=2.0-M3 plugin:download
> becomes
> a run of the plugin:download task with 3 arguments(keys)
> artifactId maven-jetspeed2-plugin
> groupId jetspeed2
> version 2.0-M3
>
> This seems to work but when I try to run the jetspeed2: build.portal I
> get the following output.
>
Note, Ive stopped using the Maven plugin for Eclipse. It was causing me
lots of problems with my Maven cache.
If you have previously built with M4, recommend cleaning out all Maven
caches such as:
rm $MAVEN_HOME/plugins/maven-jetspeed2*.jar
rm
$HOME/.maven/repository/jetspeed2/plugins/maven-jetspeed2-plugin-2.0-M4-SNAPSHOT.jar
rm -R $HOME/.maven/plugins/maven-jetspeed2-plugin-2.0-M4-SNAPSHOT
rm -R $HOME/.maven/cache/maven-jetspeed2-plugin-2.0-M4-SNAPSHOT
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org