Hi Ron,
On 5/6/07, Ron Wheeler <[EMAIL PROTECTED]> wrote:
It would seem reasonable that I should change the groupId and artifactID
to something that describes my project.
I did this when I first started working with Jetspeed. And I did so to
contribute and follow the evolution of Jetspeed. Today I wouldn't do
that. I've got one project that is going to take a while to merge with
the latest from subversion because I did just what you are describing.
So I would use the archetype to generate a custom portal. My
experience is that the source code changes very fast and it is
preferable to follow a migration guide from one version to another.
I know that waiting for new versions is not always easy so I suggest
that you use the archetype. Then keep a separate subversion build that
you use to test new archetypes or Jetspeed features you need to
integrate into your portal.
My last thought is if you want to be lazy then run one j2 subversion
build and continue to use the archetype without changing the j2
source. If you come up with a good feature then you can contribute to
the well being of j2 and your project can be tested with the latest.
If you do this then write a separate settings.xml and keep a separate
m2 repository. One for the project and one for j2 latest. Any way you
look at it requires managing separate build environments.
Philip
What problems is this going to cause besides making all of the pom.xml
files all custom to my projects?
I understand that I have to change all of the parent records in the
subsiduary pom.xml files..
<groupId>org.apache.portals.jetspeed-2</groupId>
<artifactId>jetspeed-2</artifactId>
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Philip Donaghy
donaghy.blogspot.com del.icio.us/donaghy/philip
Skype: philipmarkdonaghy
Office: +33 5 56 60 88 02
Mobile: +33 6 20 83 22 62
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
