AppFuse

Group archetypes under org.appfuse.archetypes.*

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0-M2, 2.0-M3, 2.0-M4, 2.0-M5, 2.0-RC1
  • Fix Version/s: 2.0-RC1
  • Component/s: Build, Test, or Deploy Process
  • Labels:
    None

Description

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/).

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Matt Raible added a comment -

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.

Show
Matt Raible added a comment - 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.
Hide
Permalink
Matt Raible added a comment -

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.

Show
Matt Raible added a comment - 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.
Hide
Permalink
Abel Mui?o added a comment -

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.

Show
Abel Mui?o added a comment - 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.
Hide
Permalink
Matt Raible added a comment -

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.

Show
Matt Raible added a comment - 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.
Hide
Permalink
Abel Mui?o added a comment -

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).

Show
Abel Mui?o added a comment - 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).
Hide
Permalink
Matt Raible added a comment -

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

Show
Matt Raible added a comment - Re-opening because appfuse-archetypes and appfuse-core do not have org.appfuse.archetypes as groupId.
Hide
Permalink
Matt Raible added a comment -

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?

Show
Matt Raible added a comment - 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?
Hide
Permalink
Matt Raible added a comment -

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

Show
Matt Raible added a comment - http://static.appfuse.org/repository/org/appfuse/archetypes/
Hide
Permalink
Abel Mui?o added a comment -

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).

Show
Abel Mui?o added a comment - 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).
Hide
Permalink
Matt Raible added a comment -

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.

Show
Matt Raible added a comment - 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.
Hide
Permalink
Abel Mui?o added a comment -

That's right.

Show
Abel Mui?o added a comment - That's right.

People

  • Assignee:
    Matt Raible
    Reporter:
    Abel Mui?o
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: