Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jms-dev] [jakartaee-spec-project-leads] EJB and JMS deploy permissions
Thanks, Arjan.  Looks good:


Quick question before you sleep.  Is there a way to get PDF and HTML zip file from the build output or do we need to rebuild locally?


-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com

On Jul 22, 2019, at 4:08 PM, arjan tijms <arjan.tijms@xxxxxxxxx> wrote:

Hi,

The API project should not reference the project parent, but the main EE4J parent:

    <parent>
        <groupId>org.eclipse.ee4j</groupId>
        <artifactId>project</artifactId>
        <version>1.0.5</version>
    </parent>

    <groupId>jakarta.jms</groupId>
    <artifactId>jakarta.jms-api</artifactId>
    <version>2.0.3-SNAPSHOT</version>


All the other projects have something similar. 

For correctness it should maybe include an empty relative path though, like was done here:


Kind regards,
Arjan


On Tue, Jul 23, 2019 at 1:04 AM David Blevins <david.blevins@xxxxxxxxx> wrote:
Switching over to jms-dev@

Tried my PR, didn't work :)  Doing the BUILD_DIR update now to see if that is better.  My main question with that one is the parent pom won't be deployed, so how will people be able to use the api artifact given it references the parent?
On Jul 22, 2019, at 3:59 PM, arjan tijms <arjan.tijms@xxxxxxxxx> wrote:

Hi,

Still awake, but to retain somewhat of a normal day-night rhythm I'd better go to bed about now ;)

I just approved the changes, if there's anything else let me know. Switching to the API folder is fully supported in the script, as more projects had that requirement (even before we introduced the spec folder and moved the main code to the api/ folder for some projects).

But whatever works ;)

Kind regards,
Arjan



On Tue, Jul 23, 2019 at 12:42 AM David Blevins <david.blevins@xxxxxxxxx> wrote:
Happy to accept any help.  I'm on the Jakarta EE development slack if you're still awake.

I made this PR so we can hopefully release from the root directory.

 - https://github.com/eclipse-ee4j/jms-api/pull/234


On Jul 22, 2019, at 3:25 PM, arjan tijms <arjan.tijms@xxxxxxxxx> wrote:

Hi David,

For the JMS job, the workspace path needs to be set to api only, otherwise it'll try to deploy the spec, which of course won't work.

# Directory with project top level pom.xml
BUILD_DIR="${WORKSPACE}"

should become:

# Directory with project top level pom.xml
BUILD_DIR="${WORKSPACE}/api"

I'd make the change myself otherwise, but maybe you're also working on it right now.

After that you can update the version numbers for the newly staged artefact in 2_messaging-run-tck-against-staged-build

(it has already completed once against the previous 2.02 version)

Kind regards,
Arjan






On Mon, Jul 22, 2019 at 10:08 PM David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
Thanks, Dmitry.  Found them both and am in process with the JMS api.

On Jul 22, 2019, at 1:04 PM, Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx> wrote:

EE4J artifacts are deployed to OSSRH using Eclipse Jenkins only. Only Eclipse Jenkins has credentials to deploy to OSSRH. These jobs must've been created already because we already deployed JMS and EJB.

-- Dmitry

On 22.07.2019 20:51, David Blevins wrote:
What is the process of getting permissions to deploy to jakarta.* groupIds on OSSRH?

I filed two requests with Sonatype:


However, I didn't really see any similar requests, so wondering if this is a wrong turn.


_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads

_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads

_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads

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

Back to the top