Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deploy first beta release to maven central #5

Closed
maybeec opened this issue May 12, 2016 · 7 comments
Closed

deploy first beta release to maven central #5

maybeec opened this issue May 12, 2016 · 7 comments
Assignees
Labels

Comments

@maybeec
Copy link
Owner

maybeec commented May 12, 2016

No description provided.

@maybeec maybeec self-assigned this May 12, 2016
@maybeec maybeec added the scm/ci label May 12, 2016
@maybeec
Copy link
Owner Author

maybeec commented May 12, 2016

waiting for https://issues.sonatype.org/browse/OSSRH-22393 to get resolved.

@maybeec
Copy link
Owner Author

maybeec commented Jun 2, 2016

@themetalone please check the release on staging repository to work properly with CobiGen. The staging repository is https://oss.sonatype.org/content/repositories/comgithubmaybeec-1000/.
Just check the resolution and compatibility locally by temporarily including the repository in CobiGen's pom.

@themetalone
Copy link
Collaborator

I tried to check but ran into some problems. Following Mavens Guide to Testing staged repositories I added an profile to the xml-plugin pom. Although, Eclipse still cannot find it but running a mvn clean install -Pstaged-releases only tells me that some CobiGen dependencies cannot be resolved.

@maybeec
Copy link
Owner Author

maybeec commented Jun 3, 2016

Can you post your exact snippet added?
Can you please also delete all lexeme libraries from your local repository first or run mvn with -U parameter.

@themetalone
Copy link
Collaborator

themetalone commented Jun 3, 2016

At the moment the maven build doenst work but probably because of my setup:

I added the following to the pom

    <dependency>
      <artifactId>lexeme</artifactId>
      <groupId>com.github.maybeec</groupId>
      <version>1.0.0</version>
    </dependency>
  </dependencies>

  <profiles>
    <profile>
      <id>staged-releases</id>
      <pluginRepositories>
        <pluginRepository>
          <id>staged-releases</id>
          <url>https://oss.sonatype.org/content/repositories/comgithubmaybeec-1000/</url>
        </pluginRepository>
      </pluginRepositories>
    </profile>
 </profiles>

and got

PS A:\xml\cobigen\cobigen-xmlplugin> mvn clean install -Pstaged-releases -U
[INFO] ------------------------------------------------------------------------
[INFO] Building CobiGen - XML Plug-In 2.2.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading: https://repo.maven.apache.org/maven2/com/capgemini/cobigen-core/1.2.0/cobigen-core-1.2.0.pom
[WARNING] The POM for com.capgemini:cobigen-core:jar:1.2.0 is missing, no dependency information available
Downloading: https://repo.maven.apache.org/maven2/com/github/maybeec/lexeme/1.0.0/lexeme-1.0.0.pom
[WARNING] The POM for com.github.maybeec:lexeme:jar:1.0.0 is missing, no dependency information available
Downloading: https://repo.maven.apache.org/maven2/com/capgemini/cobigen-core/1.2.0/cobigen-core-1.2.0.jar
Downloading: https://repo.maven.apache.org/maven2/com/github/maybeec/lexeme/1.0.0/lexeme-1.0.0.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project cobigen-xmlplugin: Could not resolve dependencies for project com.capgemini:co
bigen-xmlplugin:jar:2.2.0-SNAPSHOT: The following artifacts could not be resolved: com.capgemini:cobigen-core:jar:1.2.0,
 com.github.maybeec:lexeme:jar:1.0.0: Could not find artifact com.capgemini:cobigen-core:jar:1.2.0 in central (https://r
epo.maven.apache.org/maven2) -> [Help 1]

@maybeec
Copy link
Owner Author

maybeec commented Jun 3, 2016

did you open up console with console.bat? seems that nexus is not registered as a repository.
Today, I am also available at the university the whole day. So if you like, come around.

@themetalone
Copy link
Collaborator

I think I'll do that before 11:30

maybeec added a commit that referenced this issue Jun 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants