Just a comment,
I notice that you have renamed the artifacts from shindig-common to
common etc.
The reason for shindig-common was when they get deployed into a
production environment they appear as
WEB-INF/lib/common-0.1.jar
Which is a bit confusing if there are 20 or so other jars from
various sources..... common what ? common-collections ?
The only way you can find out what the jar is, once its detached from
the groupId is to unpack the jar. It probably doesn't matter so much
for social-api and gadgets, but common and server are so generic they
could be from anywhere.
Just a thought.
Ian
On 6 May 2008, at 01:05, Vincent Siveton (JIRA) wrote:
[ https://issues.apache.org/jira/browse/SHINDIG-232?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Siveton updated SHINDIG-232:
------------------------------------
Attachment: SHINDIG-232.patch
Trivial patch which:
- respects 2 spaces
- clean formats
- using <dependencyManagement/> for project versions
- renamed some project dependencies to be more consistent
Improve the Maven build due to SHINDIG-207
------------------------------------------
Key: SHINDIG-232
URL: https://issues.apache.org/jira/browse/
SHINDIG-232
Project: Shindig
Issue Type: Improvement
Reporter: Vincent Siveton
Priority: Trivial
Attachments: SHINDIG-232.patch
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
