Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-build] Parent pom 1.0.5 released
Hi,

I tried what you said, and the output of the script is:

[INFO]  * Upload of locally staged artifacts finished.
[INFO]  * Closing staging repository with ID "jakartasecurityjacc-1003".

Waiting for operation to complete...
......

[INFO] Remote staged 1 repositories, finished with success.

The script hides the information, but it appears after searching for some time that the staging ends up here:


So it seems it finally works! Thx!

Maybe it would be a good idea to print the directory from the script, or mention this repo somewhere?

Kind regards,
Arjan



On Mon, Nov 12, 2018 at 8:41 PM Tomas Kraus <tomas.kraus@xxxxxxxxxx> wrote:

With 1.0.5 parent deploy target will go trough nexux plugin and close deployment. If you are using copy of my scripts, replace MVN_DEPLOY_ARGS='deploy:deploy' with MVN_DEPLOY_ARGS='nexus-staging:deploy' and it will work too.

I already answered this to Jim:

problem in jakartaee-stable project is in wrong OSSRH profiles setup.

If you check https://jenkins.eclipse.org/jakartaee-stable/job/nexus-staging/24/console output, you'll see list of profiles configured for jakartaee-stable:

[INFO] 7edbe315063867  BOTH   Central Bundles               
[INFO] 70f72c5a53adb4  BOTH   jakarta.management.j2ee

Here is a list of profiles in metro project:

[INFO] 7edbe315063867  BOTH   Central Bundles               
[INFO] 70f899f21e20bd  BOTH   com.sun.wts.tools.ant         
[INFO] 70f899ae8d65f9  BOTH   com.sun.xml.messaging.saaj    
[INFO] 70fa302c4b5e18  BOTH   com.sun.xml.rpc               
[INFO] 70f83490d1fb38  BOTH   com.sun.xml.stream.buffer     
[INFO] 70f858851cce46  BOTH   com.sun.xml.ws                
[INFO] 70f9e844006a20  BOTH   javax.xml                     
[INFO] 64aaddb9429146  BOTH   org.glassfish                 
[INFO] 70f857fe3a5334  BOTH   org.glassfish.metro           
[INFO] 70f85cb96b6607  BOTH   org.jvnet.mimepull

-> each groupId (subproject) has its own profile.

OSSRH must add profile for each of your project (groupId) too.

I already tested closing jakartaee-stable artifacts in Central Bundles profile, but it was not working.

Tomas


Dne 12.11.18 v 21:27 arjan tijms napsal(a):
Thanks!

Is there any recommended way to run the Jenkins script now?

If I just update to 1.0.5 parent and rebuild the Jenkins job, it again deploys to this nasty unreachable staging repo. In case of JACC that is:


This still results in:

-----------
Access Denied

Please login before attempting further requests.
-----------

Kind regards,
Arjan


On Mon, Nov 12, 2018 at 7:55 PM Tomas Kraus <tomas.kraus@xxxxxxxxxx> wrote:
Hi All,

we have parent pom 1.0.5 in maven central. I tested it with Metro
project and it works fine.

Now we have nexus plugin config available in parent so nexus repository
manipulation will be more easy.


Tomas

_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build

_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build

Back to the top