10:45 a.m.
Relax the unique artifact validation rule for non-jar artifacts
---------------------------------------------------------------
Key: JBBUILD-696
URL: https://issues.jboss.org/browse/JBBUILD-696
Project: JBoss Build System
Issue Type: Feature Request
Reporter: Bob McWhirter
Assignee: Paul Gier
Sometimes we have non-changing-between-releases artifacts in our build. Nexus currently
disallows identical bytes to exist under multiple versions. When the artifact is a simple
text file, such as a Javascript script, having to introduce artifact changes to the source
is goofy.
If we could disable the uniqueness validation, at least for non-.jar/.war artifacts,
that'd be lovely.
{noformat}
Staging Artifact Uniqueness Validation
-Artifact is not unique: 'org.projectodd.stilts:stilts-stomp-client-js:0.1.9'
in repository 'thirdparty-releases' is same as
'/org/projectodd/stilts/stilts-stomp-client-js/0.1.10/stilts-stomp-client-js-0.1.10.js'
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:04 a.m.
New subject: [JBoss JIRA] Updated: (JBBUILD-696) Relax the unique artifact validation rule for non-jar artifacts
[
https://issues.jboss.org/browse/JBBUILD-696?page=com.atlassian.jira.plugi...
]
Paul Gier updated JBBUILD-696:
------------------------------
Fix Version/s: Build Support 2011
Priority: Minor (was: Major)
Component/s: Artifact Repositories
Relax the unique artifact validation rule for non-jar artifacts
---------------------------------------------------------------
Key: JBBUILD-696
URL: https://issues.jboss.org/browse/JBBUILD-696
Project: JBoss Build System
Issue Type: Feature Request
Components: Artifact Repositories
Reporter: Bob McWhirter
Assignee: Paul Gier
Priority: Minor
Fix For: Build Support 2011
Sometimes we have non-changing-between-releases artifacts in our build. Nexus currently
disallows identical bytes to exist under multiple versions. When the artifact is a simple
text file, such as a Javascript script, having to introduce artifact changes to the source
is goofy.
If we could disable the uniqueness validation, at least for non-.jar/.war artifacts,
that'd be lovely.
{noformat}
Staging Artifact Uniqueness Validation
-Artifact is not unique: 'org.projectodd.stilts:stilts-stomp-client-js:0.1.9'
in repository 'thirdparty-releases' is same as
'/org/projectodd/stilts/stilts-stomp-client-js/0.1.10/stilts-stomp-client-js-0.1.10.js'
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:04 a.m.
New subject: [JBoss JIRA] Commented: (JBBUILD-696) Relax the unique artifact validation rule for non-jar artifacts
[
https://issues.jboss.org/browse/JBBUILD-696?page=com.atlassian.jira.plugi...
]
Paul Gier commented on JBBUILD-696:
-----------------------------------
I created a Nexus Pro issue to request this improvement.
https://issues.sonatype.org/browse/NXCM-3122
Relax the unique artifact validation rule for non-jar artifacts
---------------------------------------------------------------
Key: JBBUILD-696
URL: https://issues.jboss.org/browse/JBBUILD-696
Project: JBoss Build System
Issue Type: Feature Request
Reporter: Bob McWhirter
Assignee: Paul Gier
Fix For: Build Support 2011
Sometimes we have non-changing-between-releases artifacts in our build. Nexus currently
disallows identical bytes to exist under multiple versions. When the artifact is a simple
text file, such as a Javascript script, having to introduce artifact changes to the source
is goofy.
If we could disable the uniqueness validation, at least for non-.jar/.war artifacts,
that'd be lovely.
{noformat}
Staging Artifact Uniqueness Validation
-Artifact is not unique: 'org.projectodd.stilts:stilts-stomp-client-js:0.1.9'
in repository 'thirdparty-releases' is same as
'/org/projectodd/stilts/stilts-stomp-client-js/0.1.10/stilts-stomp-client-js-0.1.10.js'
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:04 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBBUILD-696) Relax the unique artifact validation rule for non-jar artifacts
[
https://issues.jboss.org/browse/JBBUILD-696?page=com.atlassian.jira.plugi...
]
Paul Gier edited comment on JBBUILD-696 at 8/17/11 12:04 PM:
-------------------------------------------------------------
I created a Nexus Pro issue to request this improvement.
https://issues.sonatype.org/browse/NXCM-3122
Temporary workaround is to include the current project version in the Javascript and other
text files.
was (Author: pgier):
I created a Nexus Pro issue to request this improvement.
https://issues.sonatype.org/browse/NXCM-3122
Relax the unique artifact validation rule for non-jar artifacts
---------------------------------------------------------------
Key: JBBUILD-696
URL: https://issues.jboss.org/browse/JBBUILD-696
Project: JBoss Build System
Issue Type: Feature Request
Components: Artifact Repositories
Reporter: Bob McWhirter
Assignee: Paul Gier
Priority: Minor
Fix For: Build Support 2011
Sometimes we have non-changing-between-releases artifacts in our build. Nexus currently
disallows identical bytes to exist under multiple versions. When the artifact is a simple
text file, such as a Javascript script, having to introduce artifact changes to the source
is goofy.
If we could disable the uniqueness validation, at least for non-.jar/.war artifacts,
that'd be lovely.
{noformat}
Staging Artifact Uniqueness Validation
-Artifact is not unique: 'org.projectodd.stilts:stilts-stomp-client-js:0.1.9'
in repository 'thirdparty-releases' is same as
'/org/projectodd/stilts/stilts-stomp-client-js/0.1.10/stilts-stomp-client-js-0.1.10.js'
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4838
days inactive
4838
days old
3 comments
2 participants
participants (2)
-
Bob McWhirter (JIRA) -
Paul Gier (JIRA)