You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Henning Schmiedehausen (JIRA)" <de...@velocity.apache.org> on 2007/03/08 00:53:24 UTC
[jira] Created: (VELOCITY-526) Update our maven POM to match Apache
standards.
Update our maven POM to match Apache standards.
-----------------------------------------------
Key: VELOCITY-526
URL: https://issues.apache.org/jira/browse/VELOCITY-526
Project: Velocity
Issue Type: Improvement
Components: Engine
Affects Versions: 1.6
Reporter: Henning Schmiedehausen
Assigned To: Henning Schmiedehausen
Priority: Minor
The following points are open
- POM should extend the standard org.apache POM, this would reduce the amount of configuration from our POM.
- POM and jar should be signed when deployed.
- Strictly spoken, the POM itself can/should be voted on (we did vote on the POM as part of the last release)
- We should also deploy a sources / javadoc jar
- Maybe use the maven-ant tasks (http://maven.apache.org/ant-tasks.html) for deployment .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Commented: (VELOCITY-526) Update our maven POM to match
Apache standards.
Posted by "Will Glass-Husain (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548301 ]
Will Glass-Husain commented on VELOCITY-526:
--------------------------------------------
thank! I changed the packaging clause.
> Update our maven POM to match Apache standards.
> -----------------------------------------------
>
> Key: VELOCITY-526
> URL: https://issues.apache.org/jira/browse/VELOCITY-526
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 1.6
> Reporter: Henning Schmiedehausen
> Assignee: Henning Schmiedehausen
> Priority: Minor
>
> The following points are open
> - POM should extend the standard org.apache POM, this would reduce the amount of configuration from our POM.
> - POM and jar should be signed when deployed.
> - Strictly spoken, the POM itself can/should be voted on (we did vote on the POM as part of the last release)
> - We should also deploy a sources / javadoc jar
> - Maybe use the maven-ant tasks (http://maven.apache.org/ant-tasks.html) for deployment .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Commented: (VELOCITY-526) Update our maven POM to match
Apache standards.
Posted by "Laurie Chan (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548138 ]
Laurie Chan commented on VELOCITY-526:
--------------------------------------
The packaging entry for the pom file in v1.5 is incorrect going from the copy at:
http://repo1.maven.org/maven2/org/apache/velocity/velocity/1.5/
It states: <packaging>pom</packaging>
and should be <packaging>jar</packaging>
With the incorrect packaging clause a maven deploy-file will lose the jar file.
>From a quick browse of the subversion trunk it appears this is still incorrect for the engine component but has been set correctly for velocity-tools.
> Update our maven POM to match Apache standards.
> -----------------------------------------------
>
> Key: VELOCITY-526
> URL: https://issues.apache.org/jira/browse/VELOCITY-526
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 1.6
> Reporter: Henning Schmiedehausen
> Assignee: Henning Schmiedehausen
> Priority: Minor
>
> The following points are open
> - POM should extend the standard org.apache POM, this would reduce the amount of configuration from our POM.
> - POM and jar should be signed when deployed.
> - Strictly spoken, the POM itself can/should be voted on (we did vote on the POM as part of the last release)
> - We should also deploy a sources / javadoc jar
> - Maybe use the maven-ant tasks (http://maven.apache.org/ant-tasks.html) for deployment .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Issue Comment Edited: (VELOCITY-526) Update our maven POM to
match Apache standards.
Posted by "Will Glass-Husain (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548301 ]
wglass edited comment on VELOCITY-526 at 12/4/07 9:01 AM:
---------------------------------------------------------------------
thanks! I changed the packaging clause.
was (Author: wglass):
thank! I changed the packaging clause.
> Update our maven POM to match Apache standards.
> -----------------------------------------------
>
> Key: VELOCITY-526
> URL: https://issues.apache.org/jira/browse/VELOCITY-526
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 1.6
> Reporter: Henning Schmiedehausen
> Assignee: Henning Schmiedehausen
> Priority: Minor
>
> The following points are open
> - POM should extend the standard org.apache POM, this would reduce the amount of configuration from our POM.
> - POM and jar should be signed when deployed.
> - Strictly spoken, the POM itself can/should be voted on (we did vote on the POM as part of the last release)
> - We should also deploy a sources / javadoc jar
> - Maybe use the maven-ant tasks (http://maven.apache.org/ant-tasks.html) for deployment .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Resolved: (VELOCITY-526) Update our maven POM to match
Apache standards.
Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Bubna resolved VELOCITY-526.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.6
I believe these have all been taken care of now.
> Update our maven POM to match Apache standards.
> -----------------------------------------------
>
> Key: VELOCITY-526
> URL: https://issues.apache.org/jira/browse/VELOCITY-526
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 1.6
> Reporter: Henning Schmiedehausen
> Assignee: Henning Schmiedehausen
> Priority: Minor
> Fix For: 1.6
>
>
> The following points are open
> - POM should extend the standard org.apache POM, this would reduce the amount of configuration from our POM.
> - POM and jar should be signed when deployed.
> - Strictly spoken, the POM itself can/should be voted on (we did vote on the POM as part of the last release)
> - We should also deploy a sources / javadoc jar
> - Maybe use the maven-ant tasks (http://maven.apache.org/ant-tasks.html) for deployment .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org