[jira] Created: (MAVENUPLOAD-2361) Hibernate Search 3.1.0.GA
Hibernate Search 3.1.0.GA - Key: MAVENUPLOAD-2361 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2361 Project: Maven Upload Requests Issue Type: Task Reporter: Olivier Billard Attachments: hibernate-search-3.1.0.GA-bundle.jar May I ask you to upload this new GA version of Hibernate Search, please ? You can also find this artifact in the JBoss repo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2361) Hibernate Search 3.1.0.GA
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165925#action_165925 ] Olivier Billard commented on MAVENUPLOAD-2361: -- For info, I slightly changed to POM : - added the license, - changed commons-codec groupId to match central artifact (commons-codec instead of org.apache.commons) Comments inside the POM. > Hibernate Search 3.1.0.GA > - > > Key: MAVENUPLOAD-2361 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2361 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Olivier Billard > Attachments: hibernate-search-3.1.0.GA-bundle.jar > > > May I ask you to upload this new GA version of Hibernate Search, please ? > You can also find this artifact in the JBoss repo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MAVENUPLOAD-2361) Hibernate Search 3.1.0.GA
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Billard reopened MAVENUPLOAD-2361: -- Sorry, the bundle was wrong, jar file was not taken into account correctly, my fault. Here is a correct one. > Hibernate Search 3.1.0.GA > - > > Key: MAVENUPLOAD-2361 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2361 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Olivier Billard >Assignee: Carlos Sanchez > Attachments: hibernate-search-3.1.0.GA-bundle.jar > > > May I ask you to upload this new GA version of Hibernate Search, please ? > You can also find this artifact in the JBoss repo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MAVENUPLOAD-2361) Hibernate Search 3.1.0.GA
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168019#action_168019 ] Olivier Billard edited comment on MAVENUPLOAD-2361 at 3/5/09 10:24 AM: --- This one is the correct one (443 Ko) was (Author: obillard): This one is the correct one. > Hibernate Search 3.1.0.GA > - > > Key: MAVENUPLOAD-2361 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2361 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Olivier Billard >Assignee: Carlos Sanchez > Attachments: hibernate-search-3.1.0.GA-bundle.jar, > hibernate-search-3.1.0.GA-bundle.jar > > > May I ask you to upload this new GA version of Hibernate Search, please ? > You can also find this artifact in the JBoss repo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MAVENUPLOAD-2361) Hibernate Search 3.1.0.GA
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Billard updated MAVENUPLOAD-2361: - Attachment: hibernate-search-3.1.0.GA-bundle.jar This one is the correct one. > Hibernate Search 3.1.0.GA > - > > Key: MAVENUPLOAD-2361 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2361 > Project: Maven Upload Requests > Issue Type: Task >Reporter: Olivier Billard >Assignee: Carlos Sanchez > Attachments: hibernate-search-3.1.0.GA-bundle.jar, > hibernate-search-3.1.0.GA-bundle.jar > > > May I ask you to upload this new GA version of Hibernate Search, please ? > You can also find this artifact in the JBoss repo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (ARCHETYPE-156) Incorrect after using archetype:create
[
http://jira.codehaus.org/browse/ARCHETYPE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=178036#action_178036
]
Olivier Billard commented on ARCHETYPE-156:
---
I also find this behavior very restrictive concerning flat hierarchies.
Here is a small patch to permit using a flat hierarchy.
It introduces a {{flatHierarchy}} boolean parameter in the
archetype-metadata.xml root element :
{code:xml}
(...)
{code}
Effect is that modules that does not define a specific parent (such as the
parent module itself) are not added with any parent.
I had to introduce an additional parameter, as signatures only reference
{{AbstractArchetypeDescriptor}}, and not the generated {{ArchetypeDescriptor}}
that contains the parameter. If you find a better solution...
This patch applies to trunk.
*Note :* Concerning parent _modification_ on submodules, this behavior is fixed
in version 2.0-alpha-5, by depending on a newer release of maven-model. Adding
this patch will fix both issues (this issue and the flat hierarchy).
> Incorrect after using archetype:create
> ---
>
> Key: ARCHETYPE-156
> URL: http://jira.codehaus.org/browse/ARCHETYPE-156
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
> Environment: Windows XP
> Maven 2.0.7
>Reporter: Per Lindfors
>Priority: Minor
>
> Hi,
> I'm not sure if this is a bug or lack of functionality, but here it goes...
> It seems that the archetype plugin (2.0-alpha-2) and the create-goal somehow
> alters the information in the segment of the resulting pom compared
> to what we have in the "template" pom.
> In my case we would like to be able to have a root pom project with multiple
> modules(ejb, war, jar etc). Each module has a which points to a
> "super pom" in our repository instead of the root pom project. When creating
> the modules with our archetype the module gets registred in the
> segment in the root pom project, but the segment with groupId and
> artifactId etc referes not to the "super pom" in our repo, but to the root
> project. Why?
> Desired result:
> Root project pom.xml
> ---
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> se.xxx.yyy
> yyy
> 1.0-SNAPSHOT
> pom
>
>
>..
>
>
> project1
> project2
> project3
>
> Modules pom.xml
> --
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
>
> superpom-groupid
> superpom-artifactId
> superpom-version
>
> se.aaa.bbb
> project1
> 1.0-SNAPSHOT
> war
> ...
> /Per
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ARCHETYPE-156) Incorrect after using archetype:create
[ http://jira.codehaus.org/browse/ARCHETYPE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Billard updated ARCHETYPE-156: -- Attachment: flatHierarchySupport.patch Here is the patch > Incorrect after using archetype:create > --- > > Key: ARCHETYPE-156 > URL: http://jira.codehaus.org/browse/ARCHETYPE-156 > Project: Maven Archetype > Issue Type: Bug > Components: Plugin > Environment: Windows XP > Maven 2.0.7 >Reporter: Per Lindfors >Priority: Minor > Attachments: flatHierarchySupport.patch > > > Hi, > I'm not sure if this is a bug or lack of functionality, but here it goes... > It seems that the archetype plugin (2.0-alpha-2) and the create-goal somehow > alters the information in the segment of the resulting pom compared > to what we have in the "template" pom. > In my case we would like to be able to have a root pom project with multiple > modules(ejb, war, jar etc). Each module has a which points to a > "super pom" in our repository instead of the root pom project. When creating > the modules with our archetype the module gets registred in the > segment in the root pom project, but the segment with groupId and > artifactId etc referes not to the "super pom" in our repo, but to the root > project. Why? > Desired result: > Root project pom.xml > --- > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > se.xxx.yyy > yyy > 1.0-SNAPSHOT > pom > > >.. > > > project1 > project2 > project3 > > Modules pom.xml > -- > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > > superpom-groupid > superpom-artifactId > superpom-version > > se.aaa.bbb > project1 > 1.0-SNAPSHOT > war > ... > /Per -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
