-
1. Re: Snapshots
Also I'd prefer to do a proper release, but this page is useless for undertanding this.
http://wiki.jboss.org/wiki/Wiki.jsp?page=Maven
We need a "repository deploy" procedure, which should be a checklist,
including manual checks like:
* the version policy (how do you decide what the next version is)
* move the pom.xml onto the next release/snapshot when finished?
* tagging (how the maven version relates to SVN tags)
* a release cannot depend on snapshots (how to resolve when it does)
* all tests must pass (QA approved release?).
* all JIRA issues should be closed
* JIRA needs updating to move along the released project
* Notifying product support about the new release (where relevant)
* Agreement from project lead
* etc.
The current page does not even describe what is automated.
Ideally this should be a simple page with links to the details. -
2. Re: Snapshots
"adrian@jboss.org" wrote:
I'm confused by the snapshots.
My thoughts exactly. :-)"adrian@jboss.org" wrote:
I'm trying to update the current jboss-test snapshot (1.0.4-snapshot).
So if I understand, you succeeded?
Since I was about to do it - because of the changes that I made - moving some MC test code into jboss-test.
But I see you still didn't remove the code + todos on the classloader test code. -
3. Re: Snapshots
"adrian@jboss.org" wrote:
But I also got an error about not configuring the repository.jboss.com
I thought the idea was that the new snapshots don't get updated there?[INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] One or more required plugin parameters are invalid/missing for 'jboss-deploy:jboss-deploy' [0] inside the definition for plugin: 'jboss-deploy-maven-plugin'specify the following: <configuration> ... <jbossDeployRoot>VALUE</jbossDeployRoot> </configuration> -OR- on the command line, specify: '-Djboss.repository.root=VALUE'
These messages are coming from the jboss-deploy-maven plugin. By default jboss-test will deploy to both the maven repository, and the non-maven (jboss build) repository.
The maven snapshot deployment seemed to work ok for you. The error message was letting you know that if you want to deploy to the non-maven repository you will have to set the location of where to deploy the stuff to. I'll update the wiki and the error messages to make this less confusing.
The wagon version is just the plugin that let's deployment happen over webdav. You can ignore that. -
4. Re: Snapshots
"adrian@jboss.org" wrote:
Also I'd prefer to do a proper release, but this page is useless for undertanding this.
http://wiki.jboss.org/wiki/Wiki.jsp?page=Maven
We need a "repository deploy" procedure, which should be a checklist,
including manual checks like:
* the version policy (how do you decide what the next version is)
* move the pom.xml onto the next release/snapshot when finished?
* tagging (how the maven version relates to SVN tags)
* a release cannot depend on snapshots (how to resolve when it does)
* all tests must pass (QA approved release?).
* all JIRA issues should be closed
* JIRA needs updating to move along the released project
* Notifying product support about the new release (where relevant)
* Agreement from project lead
* etc.
The current page does not even describe what is automated.
Ideally this should be a simple page with links to the details.
There is this page:
http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenReleaseProcess
Which you can get to from the main maven page under the heading "Releasing software with maven". Maybe this link should be more prominent?
But it is missing some of the things that you described above. I will add the above info this week. -
5. Re: Snapshots
"pgier" wrote:
"adrian@jboss.org" wrote:
But I also got an error about not configuring the repository.jboss.com
I thought the idea was that the new snapshots don't get updated there?[INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] One or more required plugin parameters are invalid/missing for 'jboss-deploy:jboss-deploy' [0] inside the definition for plugin: 'jboss-deploy-maven-plugin'specify the following: <configuration> ... <jbossDeployRoot>VALUE</jbossDeployRoot> </configuration> -OR- on the command line, specify: '-Djboss.repository.root=VALUE'
These messages are coming from the jboss-deploy-maven plugin. By default jboss-test will deploy to both the maven repository, and the non-maven (jboss build) repository.
The maven snapshot deployment seemed to work ok for you. The error message was letting you know that if you want to deploy to the non-maven repository you will have to set the location of where to deploy the stuff to. I'll update the wiki and the error messages to make this less confusing.
The wagon version is just the plugin that let's deployment happen over webdav. You can ignore that.
Just thinking some more about this issue. Maybe the plugin can prompt the user to either ignore the non-jboss deployment, or specify a deployment directory if it's not already set.
Would that be helpful? -
6. Re: Snapshots
So, what's the easies way to link the current (version of) 'external' libraries into your IDE (IntelliJ in my case)?
Is this somehow automated? Or do I have to check the pom.xml for dependencies and fetch the required libraries out of repository and link them in the IDE? -
-
8. Re: Snapshots
"alesj" wrote:
So, what's the easies way to link the current (version of) 'external' libraries into your IDE (IntelliJ in my case)?
Is this somehow automated? Or do I have to check the pom.xml for dependencies and fetch the required libraries out of repository and link them in the IDE?
There are a few maven plugins for idea that you can try:
http://plugins.intellij.net/search/?search=maven
This one might have the dependency management features that you're looking for:
http://plugins.intellij.net/plugin/?id=1223