[
http://jira.codehaus.org/browse/MNBMODULE-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120741
]
Johan Andrén commented on MNBMODULE-25:
---------------------------------------
If I look in the attached output it says version "2.7-20071220.111925-7" and if
I do a new build it says "2.7-20071220.111925-7", so it is the same.
I think the "-U" rather solved something about resolving our project snapshots.
Note that we have to run with it all the time to make the build work, not only
once to get everything updated.
When looking at the logs we se two deploys per nbm-project, first the jar-file
with one number appended and then the nbm-file with the number increased. For
example 50 and 51 in the following build output:
[INFO] Retrieving previous build number from snapshots
Uploading: http://smith:9000/artifactory/[EMAIL
PROTECTED]/se/databyran/prosang/client/core/server/1.1-SNAPSHOT/server-1.1-20080121.085611-50.jar
4K uploaded
[INFO] Retrieving previous metadata from snapshots
[INFO] Uploading repository metadata for: 'artifact
se.databyran.prosang.client.core:server'
[INFO] Retrieving previous metadata from snapshots
[INFO] Uploading project information for server 1.1-20080121.085611-50
[INFO] Retrieving previous metadata from snapshots
[INFO] Uploading repository metadata for: 'snapshot
se.databyran.prosang.client.core:server:1.1-SNAPSHOT'
[INFO] Retrieving previous build number from snapshots
Uploading: http://smith:9000/artifactory/[EMAIL
PROTECTED]/se/databyran/prosang/client/core/server/1.1-SNAPSHOT/server-1.1-20080121.085611-51.nbm
4375K uploaded
but just before the error the highest number (51) is used by maven with the
jar-dependency:
Downloading:
http://smith:9000/artifactory/repo/se/databyran/prosang/client/core/server/1.1-SNAPSHOT/server-1.1-20080121.085611-51.jar
Downloading:
http://smith:9000/artifactory/repo/se/databyran/prosang/client/core/util/1.1-SNAPSHOT/util-1.1-20080121.085611-58.jar
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
> problems with deploy on linux
> -----------------------------
>
> Key: MNBMODULE-25
> URL: http://jira.codehaus.org/browse/MNBMODULE-25
> Project: Maven 2.x Netbeans Module Plugin
> Issue Type: Bug
> Affects Versions: 2.7
> Environment: Fedora Core 6, Maven 2.0.8, JDK 1.6.0
> Reporter: Johan Andrén
> Assignee: Milos Kleint
> Fix For: 2.7
>
> Attachments: error.log
>
>
> We have a tree of netbeans modules some of which have dependencies on other
> modules in the tree something like this:
> suite
> + core
> + - server
> + - util
> + - program-menu
> + admin
> + - users
> where the modules 'program-menu' and 'user' both depend on 'server' and 'util'
> I stumbled upon this problem when i was setting up our ci-server which runs
> on fedora. When running "mvn install" the build works fine, all modules are
> built in the correct order and are installed in the user repository.
> The problem appears when we run "mvn deploy" on the fedora machine to deploy
> all artifacts to our intranet repository. The reactor summary is the same as
> on "install" so the 'server-access' project is built first and then deployed
> to the server. Next the 'program-menu' is built but the build fails claiming
> that the dependency 'server-access:jar' cannot be resolved.
> In the maven output we can see that both the .jar and the .nbm artefacts are
> deployed, we have also verified that the artifacts are indeed in the
> repository.
> When we try to verify the problem by running "mvn deploy" on an OSX
> workstation we have discovered that the problem does not exist.
> The build output with debug flag enabled is attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
