[#APF-774] Group archetypes under org.appfuse.archetypes.*

AppFuse

Group archetypes under org.appfuse.archetypes.*

Created: 25/May/07 11:43 AM Updated: 02/Sep/07 10:32 PM

Component/s:

Build, Test, or Deploy Process

Affects Version/s:

2.0-M2, 2.0-M3, 2.0-M4, 2.0-M5, 2.0-RC1

Fix Version/s:

2.0-RC1

Description

« Hide

It is easier for 3rd party tools to identify available archetypes and versions if they are isolated from other archetypes. The core maven2 archetypes are an example of this structure (see http://repo1.maven.org/maven2/org/apache/maven/archetypes/).

All

Comments

Change History

FishEye

Sort Order:

[ Permlink | « Hide ]

Matt Raible - 30/May/07 02:57 PM

This work has been done in SVN, but I'm leaving this issue open as a reminder to change the QuickStart Guide as part of releasing RC1.

[ Permlink | « Hide ]

Matt Raible - 14/Aug/07 12:47 AM

I have the infrastructure in place to get AppFuse 2.0 M5 uploaded to Maven's Central Repository. Do you think we should wait for 2.0 RC1 because of this change? It seems to make sense since we're changing the location of archetypes.

[ Permlink | « Hide ]

Abel Muiño - 14/Aug/07 06:50 PM

I think it would be easier (for coordinating with maven folks, but also for new users) to have a single location for the archetypes, so RC1 would be the first uploaded version.

However, I don't expect any problem on Candy for AppFuse if M5 is uploaded to the maven central repository, so if there is any reason for uploading M5, go ahead.

[ Permlink | « Hide ]

Matt Raible - 28/Aug/07 02:56 PM

Added warning to Quickstart Guide so this issue can be closed:

For 2.0 RC1, the archetypeGroupId has changed from org.appfuse to org.appfuse.archetypes.

[ Permlink | « Hide ]

Abel Muiño - 01/Sep/07 06:54 AM

Sorry for getting back so late.

I've just realized that the group id "org.appfuse.archetypes" also contains two non-archetype artifacts:
- appfuse-archetypes
- appfuse-core

Would it be possible to remove them before 1.0 final? (I can file a new issue for that, or this can be reopened).

[ Permlink | « Hide ]

Matt Raible - 01/Sep/07 10:45 AM

Re-opening because appfuse-archetypes and appfuse-core do not have org.appfuse.archetypes as groupId.

[ Permlink | « Hide ]

Matt Raible - 01/Sep/07 11:04 AM

In SVN, both appfuse-archetypes and appfuse-core have org.appfuse.archetypes as the groupId in their pom.xml files. Is there something else I'm missing?

[ Permlink | « Hide ]

Matt Raible - 01/Sep/07 11:13 AM

http://static.appfuse.org/repository/org/appfuse/archetypes/

[ Permlink | « Hide ]

Abel Muiño - 01/Sep/07 11:42 AM

The reason for this ticket is to isolate AppFuse archetypes from other AppFuse artifacts. This way 3rd party tools can assume that http://static.appfuse.org/repository/org/appfuse/archetypes/ contains links to poms and avoid any special filtering (by name or by looking at the poms). This is useful for creating a list of existing archetypes.

IMO, Since appfuse-archetypes and appfuse-core are not archetypes, they should *not* have the org.appfuse.archetypes groupId (org.appfuse is probably ok).

[ Permlink | « Hide ]

Matt Raible - 01/Sep/07 11:50 AM

OK - so that means that appfuse-archetypes should change its groupId to org.appfuse, since it's not an archetype. However, appfuse-core is an archetype (backend only) so it should keep its same groupId.

[ Permlink | « Hide ]

Abel Muiño - 01/Sep/07 11:56 AM

That's right.