Re: Maven Indexer questions
Le mercredi 29 mars 2017, 16:31:10 CEST Laird Nelson a écrit : > I am working with the maven-indexer componentry for the first time; please > forgive my ignorance. > > I normally wouldn't ask these questions here, but there is no documentation. did you have a look at: http://maven.apache.org/maven-indexer-archives/maven-indexer-LATEST/ http://maven.apache.org/maven-indexer-archives/maven-indexer-LATEST/indexer-core/index.html ? I'm not a Lucene expert at all, and can't really give you better info, sorry... Regards, Hervé - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Indexer questions
On Thu, Mar 30, 2017 at 9:44 AM Hervé BOUTEMY wrote: > Le mercredi 29 mars 2017, 16:31:10 CEST Laird Nelson a écrit : > > I normally wouldn't ask these questions here, but there is no > documentation. > did you have a look at: > http://maven.apache.org/maven-indexer-archives/maven-indexer-LATEST/ > > http://maven.apache.org/maven-indexer-archives/maven-indexer-LATEST/indexer-core/index.html > ? > No! I was looking at http://maven.apache.org/maven-indexer/. I've seen this pattern on the website before: sometimes there's something under foo-bar, and other times it's under foo-bar-archives/foo-bar-VERSION. Is there a cheat sheet on when to look where? Thanks for the pointers, Best, Laird
Re: Maven Indexer questions
there is the documentation for component reference documentation publication: http://maven.apache.org/developers/website/deploy-component-reference-documentation.html but nothing for end-users: the developer doc is not easy to understand, but I managed to write one. For end-users, I don't know how to write it to have a chance someone will use it... Regards, Hervé Le jeudi 30 mars 2017, 16:57:51 CEST Laird Nelson a écrit : > On Thu, Mar 30, 2017 at 9:44 AM Hervé BOUTEMY wrote: > > Le mercredi 29 mars 2017, 16:31:10 CEST Laird Nelson a écrit : > > > I normally wouldn't ask these questions here, but there is no > > > > documentation. > > did you have a look at: > > http://maven.apache.org/maven-indexer-archives/maven-indexer-LATEST/ > > > > http://maven.apache.org/maven-indexer-archives/maven-indexer-LATEST/indexe > > r-core/index.html ? > > No! I was looking at http://maven.apache.org/maven-indexer/. > > I've seen this pattern on the website before: sometimes there's something > under foo-bar, and other times it's under > foo-bar-archives/foo-bar-VERSION. Is there a cheat sheet on when to look > where? > > Thanks for the pointers, > Best, > Laird - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Getting maven to create a bundle manifest incrementally in eclipse
Hi, @Curtis Yes, I had runOnIncremental enabled, but it didn't appear to do anything. I also added rebuildBundle to no avail. @Karl Heinz I wanted away from the MF first approach due to the added complexity that comes with it in tracking everything (although I must admit I didn't really have a close look at tycho). I also upgraded eclipse to Neon2 but that helped little. I added an execution for the build when saving but then it ended up in an endless cycle of "generate MF incrementally <-> save generated MF". I couldn't find a way to ignore changes to the MF that the incremental build was generating outside of /target/. @Justin That is exactly why I switched to maven, I wanted the source first, then the POM for specifics (Activator, etc.). We are using eclipse Virgo as the server and it has integrated IDE tooling but that tooling requires that the project is also a PDE project. When I removed the PDE facets the Virgo tooling broke. I have now solved my issue by dropping the PDE and Virgo aspects (removing all "eclipse plugin" style artefacts) and relying on the m2e integration. There is one drawback in doing it this way, the IDE debugging of the code in Virgo is not available. I'll have to revisit the whole build procedure next week but I am happy to say the moving away from ant+ivy has make the whole OSGi development process a lot easier. Thanks for all the suggestions. - Bill Mair - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
buildnumber plugin - last revision vs revision
Dear All, I'd like to implement versioning of my builds based on actual SVN revisions. However, when using buildnumber plugin, it returns the revision of top level folder (repository root), not my subfolder. When running the following command in console, which seems to be executed via plugin during the build process: svn --non-interactive info C:\trunk\liferay\test-portlet I am getting the following outcome: Path: C:\trunk\liferay\test-portlet Working Copy Root Path: C:\trunk URL: https://svn.doctribute.org/svn/dev/trunk/liferay/test-portlet Relative URL: ^/trunk/liferay/test-portlet Repository Root: https://svn.doctribute.org/svn/dev Repository UUID: d2212073-805c-254b-a7b3-a8ceac86dd9a Revision: 44044 Node Kind: directory Schedule: normal Last Changed Author: j.tosovsky Last Changed Rev: 43992 Last Changed Date: 2017-03-24 16:44:15 +0100 (Fri, 24 Mar 2017) For my use I'd prefer using 'Last Changed Rev' and 'Last Changed Date' for the final buildNumber and timestamp respectively. Currently I am getting 44044, which is not the revision of my code, but the revision of other (sister) project. I've tried to modify this option (with both true/false values), but the result is same: false (I am not sure I understand the meaning of this feature) Is there any chance to utilize 'Last Changed XXX' entries? Thanks, Jan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Indexer questions
Hi Laird, sadly, not possible right now: https://issues.apache.org/jira/browse/MINDEXER-81 Lucene does handle "dynamically added" fields, but MI as it currently stands does not. On Wed, Mar 29, 2017 at 6:31 PM Laird Nelson wrote: > I am working with the maven-indexer componentry for the first time; please > forgive my ignorance. > > I normally wouldn't ask these questions here, but there is no > documentation. > > Suppose I am writing an IndexCreator implementation that wants to look at > all the META-INF/MANIFEST.MF files reachable in a repository and create > fields for each header found in them. (First off, is such dynamic field > creation even A Thing? I am no kind of Lucene expert.) > > (I'm looking to allow things like "find me artifacts that contain 'fred' in > their Class-Path manifest header" or any of a variety of other use cases > derivable from the ability to index properties-like files inside artifact > jars.) > > What, in this case, should my IndexCreator return from its (undocumented) > getIndexerFields() method? If it's called "up front", then of course I > can't return anything meaningful since I won't know the sum total of the > fields my IndexCreator will contribute until the end. If it's not called > up front, then maybe I'm OK. I don't actually see it being called in any > meaningful way at all, but I'm sure I'm missing something, which is why I > ask here. > > Next, I noticed that IndexerField has a getVersion() method, and from > spelunking some more in the source base it seems like certain IndexCreators > effectively "bump up" this version, i.e. every time a new IndexCreator > comes up with new fields it does so with a new version. That suggests that > perhaps I need to also get a constant added to IndexerFieldVersion, which > is an enum. Can I just invent a version number here (I don't see this > method called anywhere in the source base) or must I use an existing one, > or…? > > Lastly, I see that ArtifactInfo seems to have fields in it that correspond > loosely with the kinds of IndexCreators that exist (for example, it has a > classNames field, which to my naive eyes is filled in by the > JarFileContentsIndexCreator, suggesting that if you add a funky new > IndexCreator you are obliged to add new fields to ArtifactInfo, but that > coupling seems really wrong so I'm sure I'm missing something). Is that > actually true? Also, the class is marked as being "phased out", but seems > to be central to the notion of creating indices. Is there an alternative I > should be using instead? > > Thanks in advance for help with these baby steps. > > Best, > Laird > -- Thanks, ~t~
Re: buildnumber plugin - last revision vs revision
Hi Jan, On 30/03/17 22:01, Jan Tosovsky wrote: Dear All, I'd like to implement versioning of my builds based on actual SVN revisions. However, when using buildnumber plugin, it returns the revision of top level folder (repository root), not my subfolder. When running the following command in console, which seems to be executed via plugin during the build process: svn --non-interactive info C:\trunk\liferay\test-portlet I am getting the following outcome: Path: C:\trunk\liferay\test-portlet Working Copy Root Path: C:\trunk URL: https://svn.doctribute.org/svn/dev/trunk/liferay/test-portlet Relative URL: ^/trunk/liferay/test-portlet Repository Root: https://svn.doctribute.org/svn/dev Repository UUID: d2212073-805c-254b-a7b3-a8ceac86dd9a Revision: 44044 Node Kind: directory Schedule: normal Last Changed Author: j.tosovsky Last Changed Rev: 43992 Last Changed Date: 2017-03-24 16:44:15 +0100 (Fri, 24 Mar 2017) For my use I'd prefer using 'Last Changed Rev' and 'Last Changed Date' for the final buildNumber and timestamp respectively. Currently I am getting 44044, which is not the revision of my code, but the revision of other (sister) project. I've tried to modify this option (with both true/false values), but the result is same: false (I am not sure I understand the meaning of this feature) Is there any chance to utilize 'Last Changed XXX' entries? which version of the buildnumber-maven-plugin do you use? Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: buildnumber plugin - last revision vs revision
On 2017-03-30 Karl Heinz Marbaise wrote: > On 30/03/17 22:01, Jan Tosovsky wrote: > > > > I'd like to implement versioning of my builds based on actual SVN > > revisions. > > > > However, when using buildnumber plugin, it returns the revision of > > top level folder (repository root), not my subfolder. > > > > When running the following command in console, which seems to be > > executed via plugin during the build process: > > > > svn --non-interactive info C:\trunk\liferay\test-portlet > > > > I am getting the following outcome: > > > > Path: C:\trunk\liferay\test-portlet > > Working Copy Root Path: C:\trunk > > URL: https://svn.doctribute.org/svn/dev/trunk/liferay/test-portlet > > Relative URL: ^/trunk/liferay/test-portlet > > Repository Root: https://svn.doctribute.org/svn/dev > > Repository UUID: d2212073-805c-254b-a7b3-a8ceac86dd9a > > Revision: 44044 > > Node Kind: directory > > Schedule: normal > > Last Changed Author: j.tosovsky > > Last Changed Rev: 43992 > > Last Changed Date: 2017-03-24 16:44:15 +0100 (Fri, 24 Mar 2017) > > > > > > For my use I'd prefer using 'Last Changed Rev' and 'Last Changed > > Date' for the final buildNumber and timestamp respectively. > > Currently I am getting 44044, which is not the revision of my code, > > but the revision of other (sister) project. > > > > I've tried to modify this option (with both true/false values), but > > the result is same: > > false > > (I am not sure I understand the meaning of this feature) > > > > Is there any chance to utilize 'Last Changed XXX' entries? > > which version of the buildnumber-maven-plugin do you use? oops, it is 1.4. In meantime I found GitHub Pages and my issue resembles https://github.com/mojohaus/buildnumber-maven-plugin/issues/36 and also (fixed, but not released yet) https://github.com/mojohaus/buildnumber-maven-plugin/issues/38 But there is also a pull request mentioning the support for the Last Changed Date (what I need as well): https://github.com/mojohaus/buildnumber-maven-plugin/pull/16 So I most likely need to integrate that pull request and to build the custom version from sources to get correct behavior. Or is there planned any new build (the last one was in 2015)? Thanks, Jan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Indexer questions
On Thu, Mar 30, 2017 at 2:34 PM Tamás Cservenák wrote: > sadly, not possible right now: > https://issues.apache.org/jira/browse/MINDEXER-81 Thank you; I've voted for the bug, watched it and added a comment: https://issues.apache.org/jira/browse/MINDEXER-81?focusedCommentId=15949969&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15949969 Best, Laird
Re: buildnumber plugin - last revision vs revision
Hi Jan, On 31/03/17 00:18, Jan Tosovsky wrote: On 2017-03-30 Karl Heinz Marbaise wrote: On 30/03/17 22:01, Jan Tosovsky wrote: I'd like to implement versioning of my builds based on actual SVN revisions. However, when using buildnumber plugin, it returns the revision of top level folder (repository root), not my subfolder. When running the following command in console, which seems to be executed via plugin during the build process: svn --non-interactive info C:\trunk\liferay\test-portlet I am getting the following outcome: Path: C:\trunk\liferay\test-portlet Working Copy Root Path: C:\trunk URL: https://svn.doctribute.org/svn/dev/trunk/liferay/test-portlet Relative URL: ^/trunk/liferay/test-portlet Repository Root: https://svn.doctribute.org/svn/dev Repository UUID: d2212073-805c-254b-a7b3-a8ceac86dd9a Revision: 44044 Node Kind: directory Schedule: normal Last Changed Author: j.tosovsky Last Changed Rev: 43992 Last Changed Date: 2017-03-24 16:44:15 +0100 (Fri, 24 Mar 2017) For my use I'd prefer using 'Last Changed Rev' and 'Last Changed Date' for the final buildNumber and timestamp respectively. Currently I am getting 44044, which is not the revision of my code, but the revision of other (sister) project. I've tried to modify this option (with both true/false values), but the result is same: false (I am not sure I understand the meaning of this feature) Is there any chance to utilize 'Last Changed XXX' entries? which version of the buildnumber-maven-plugin do you use? oops, it is 1.4. Just fine that is the latest release of it... In meantime I found GitHub Pages and my issue resembles https://github.com/mojohaus/buildnumber-maven-plugin/issues/36 and also (fixed, but not released yet) https://github.com/mojohaus/buildnumber-maven-plugin/issues/38 But there is also a pull request mentioning the support for the Last Changed Date (what I need as well): https://github.com/mojohaus/buildnumber-maven-plugin/pull/16 So I most likely need to integrate that pull request and to build the custom version from sources to get correct behavior. Or is there planned any new build (the last one was in 2015)? Thanks, Jan At the moment I'm working on such issues...and trying to fix some of them...cause the 3.0.0 milestone has a large number of fixes in the meantime...I'm thinking of making a release of it within the next few weeks... Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: buildnumber plugin - last revision vs revision
Hi Karl Heinz, On 2017-03-31 Karl Heinz Marbaise wrote: > On 31/03/17 00:18, Jan Tosovsky wrote: > > On 2017-03-30 Karl Heinz Marbaise wrote: > >> On 30/03/17 22:01, Jan Tosovsky wrote: > >>> > >>> I'd like to implement versioning of my builds based on actual SVN > >>> revisions. > >>> > >>> However, when using buildnumber plugin, it returns the revision of > >>> top level folder (repository root), not my subfolder. > >>> > >>> When running the following command in console, which seems to be > >>> executed via plugin during the build process: > >>> > >>> svn --non-interactive info C:\trunk\liferay\test-portlet > >>> > >>> I am getting the following outcome: > >>> > >>> Path: C:\trunk\liferay\test-portlet > >>> Working Copy Root Path: C:\trunk > >>> URL: https://svn.doctribute.org/svn/dev/trunk/liferay/test-portlet > >>> Relative URL: ^/trunk/liferay/test-portlet > >>> Repository Root: https://svn.doctribute.org/svn/dev > >>> Repository UUID: d2212073-805c-254b-a7b3-a8ceac86dd9a > >>> Revision: 44044 > >>> Node Kind: directory > >>> Schedule: normal > >>> Last Changed Author: j.tosovsky > >>> Last Changed Rev: 43992 > >>> Last Changed Date: 2017-03-24 16:44:15 +0100 (Fri, 24 Mar 2017) > >>> > >>> > >>> For my use I'd prefer using 'Last Changed Rev' and 'Last Changed > >>> Date' for the final buildNumber and timestamp respectively. > >>> Currently I am getting 44044, which is not the revision of my code, > >>> but the revision of other (sister) project. > >>> > >>> I've tried to modify this option (with both true/false values), but > >>> the result is same: > >>> false > >>> (I am not sure I understand the meaning of this feature) > >>> > >>> Is there any chance to utilize 'Last Changed XXX' entries? > >> > >> which version of the buildnumber-maven-plugin do you use? > > > > oops, it is 1.4. > > Just fine that is the latest release of it... > > > > > In meantime I found GitHub Pages and my issue resembles > > https://github.com/mojohaus/buildnumber-maven-plugin/issues/36 > > > > and also (fixed, but not released yet) > > https://github.com/mojohaus/buildnumber-maven-plugin/issues/38 > > > > But there is also a pull request mentioning the support for the > > Last Changed Date (what I need as well): > > https://github.com/mojohaus/buildnumber-maven-plugin/pull/16 > > > > > > So I most likely need to integrate that pull request and to build > > the custom version from sources to get correct behavior. Or is > > there planned any new build (the last one was in 2015)? > > > > At the moment I'm working on such issues...and trying to fix some of > them...cause the 3.0.0 milestone has a large number of fixes in the > meantime...I'm thinking of making a release of it within the next > few weeks... > I'll wait then (even it will take even longer). Thanks a lot! Btw, I'd be grateful for implementing especially this one: https://github.com/mojohaus/buildnumber-maven-plugin/issues/17 ;-) Jan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
