| Take a look on how it’s done in other projects which have released to OSSRH staging:
— Dmitry
Hi, Even after updating to 1.0.4, build didn't work. Only after I add
the below repository configuration, my build goes fine. I believe
this needs to be added in parent pom to avoid duplication. Thanks, Vinay
On 02/11/18 2:57 PM, Dmitry Kornilov
wrote:
Use version 1.0.4 of parent pom.
— Dmitry
Hi,
I am trying to update dependencies in
jsp-api to point to artifacts released to staging
repository. I see in parent pom, repositories
configuration does exist but it is not at the root
level but is nestled inside profiles.
Shouldn't repository configuration be added
at the root too in parent pom? I tried building the
jsp-api project locally but it fails looking for these
artifacts. I tried adding repository configuration in
project's pom too, but it still complains. This is what I tried adding in parent pom: <repositories>
<repository>
<id>sonatype-nexus-snapshots</id>
<name>Sonatype Nexus
Snapshots</name>
<url>
https://oss.sonatype.org/content/repositories/staging
</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories> Any pointer? Do I need to add a mirror in my
maven settings.xml? Thanks, Vinay
On 26/10/18 3:41 PM, Dmitry
Kornilov wrote:
Yes, you are right. OSSRH repositories are configured
in the EE4J parent pom. If your project uses it, you
are fine. If not, you need to configure it yourself in
your pom file.
— Dmitry
Hi, Just for my understanding,
in-order to other projects to be able to
uptake new Eclipse version of dependencies
available in staging repository to OSSRH,
I believe the project which is going to
consume it must add the OSSRH staging
repository in project's pom. Is this
understanding correct? Thanks, Vinay
On Friday 26
October 2018 03:05 PM, Dmitry Kornilov
wrote:
Let me clarify. November 5th deadline is
about uptake new Eclipse versions of
dependencies and releasing artifacts to
OSSRH *staging* so other projects can take
it. I see that you’ve done it already. You
are the first one! Congrats!. This is not
about the public release. You don’t need
to pass the release review in order to do
it. But I am suggesting initiating the
release review asap before the majority of
projects do it. It will make Eclipse IP
team life a bit easier.
Thanks,
Dmitry
Hi,
I just
wanted to check
something regarding the
current glassfish
release plan:
It has a
date of November 5th but
the JTA API 1.3.1
release review is not
scheduled to conclude
until November 7th:
Is that a
problem?
I would add
that the JTA API 1.3.1
release is already in
Eclipse staging since
yesterday and so I also
have a PR to upgrade
GlassFish (assuming
GlassFish can build from
dependencies in
staging):
Thanks,
Tom
_______________________________________________
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
_______________________________________________
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
_______________________________________________ ee4j-build mailing list ee4j-build@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ee4j-build
|
